ianchildress

Great explanation, that explains a lot!

These are pretty big to me:

The garbage collector is now concurrent and provides dramatically lower pause times by running, when possible, in parallel with other goroutines.

By default, Go programs run with GOMAXPROCS set to the number of cores available; in prior releases it defaulted to 1.

But how important is this? It doesn't seem like it affects the average user:

The compiler and runtime are now written entirely in Go (with a little assembler). C is no longer involved in the implementation, and so the C compiler that was once necessary for building the distribution is gone.

I signed up just to reply to this post and say THIS is exactly how our development team (which write in Go) feels. This post could not be more accurate in terms of trying to deal with the outdated documentation.

#1 The documentation is often months and many versions old.

#2 is the fact that app engine instances have to connect to back end compute engine instances using a public IP is unbelievable. The solution for an app engine instance to communicate with your compute engine app is to use their PubSub api system. To get the PubSub api system to work, see #1. The examples are months outdated and you no longer use the appengine.Context to create your OAuth token, but instead now use context.Context which you learn by going through github issue comments.

Google needs to recognize their great deficiency in documentation to be considered in the same tier as AWS.