Keep in mind this is a rant, so it likely goes over the top a bit. That said, I first hand encountered some of the constructs mentioned here... I find that surprising in such a recent language indeed.

With the little Go I wrote, I admit that the multiple return values feature is... odd. Worse though, it has bad ramifications.

An evolving list of how to write idiomatic Go.

Nice return on experience of using a simple stack to serve loads of web requests.

Interesting update. Looks like Go is making progress at its own pace and tries to stay small.

Not earth shattering benchmark, kind of confirms what we can expect on the concurrency and REST side of things: Rust, Go > .NET > JVM

This is indeed a strange default used for sockets there... will have bad consequences for sure in more situations than expected.

Wow, this is a very good exploration of the performances of several common languages and runtimes. This is one of the most thorough I've seen. A good resource for deciding what to pick.

Debatable "feature", bad implementation, dubious community handling... Clearly not a good example to follow from the Go space.

This is in part a rant but lots of points in there are very valid. This is in part why I don't find Go a very compelling option so far. Modern tooling indeed, nice runtime in some areas but leaves way too much of the complexity in imperative code.

Admittedly, the go toolchain seems to handle supply chain problems in a neat way. I especially like the VCS as the source of truth.

This is a good highlight of the differences. It's not "one is best", it is really "pick what is best in your context".

I like this kind of list of "gotchas" for languages or frameworks. This one seems to be fairly comprehensive in the case of Go. There are a few I wouldn't expect in such a recent and fashionable language, oh well...

I like when papers aren't about "mine is better than your". This is an interestingly balanced take on those two popular option showing where they fit best. Shows good reasons for a polyglot approach: as usual use the best tool for the job.

Somehow states the obvious: you don't always need docker. Still a good reminder, especially true with the trend of single binary web services like what can be achieved with Go and Rust.

This looks like an interesting intrusion detection tool. I like the overall approach they chose.