we should never blindly apply dogmatic advice, and that we should use our judgment each and every time.

If the word “share” doesn’t come out of your mouth, you don’t need to use a pointer

The benefit of passing data “by value” is readability. The value you see in the function call is what is copied and received on the other side

Functions execute within the scope of frame boundaries that provide an individual memory space for each respective function. Each frame allows a function to operate within their own context and also provides flow control. A function has direct access to the memory inside its frame, through the frame pointer, but access to memory outside its frame requires indirect access. For a function to access memory outside of its frame, that memory must be shared with the function.

The log will become something of a commoditized interface, with many algorithms and implementations competing to provide the best guarantees and optimal performance.

Go Programming Language publicly in 2009 they were also looking to solve certain challenges of the existing Computer languages. Of the many features that it demonstrated (we will get to those soon enough) it was also helpful in addressing the strange dilemma of hardware and software that was emerging.

(It's usually a mistake to pass back the concrete type of an error rather than error, for reasons discussed in the Go FAQ, but it's the right thing to do here because ServeHTTP is the only place that sees the value and uses its contents.)

There are two reasons for having no warnings. First, if it's worth complaining about, it's worth fixing in the code.

[]byte