It also helps that Filippo is very diligent and observant. He is one of the most frequent people to send in corrections or extra background information to my Go newsletter :-)

<3 to both :)

Love the newsletter. https://golangweekly.com

Go is great. But if you look close enough, go also has some dark corners.

The reason the biggest parts of go/crypto is well designed, good readable code, is mostly the work of one person (the author).

Any particular dark corners you know of?

One example, the started (and then stuck) net/ip to net/netip migration?

The tailscale netip package is great (as external pkg), but without commit to a full migration plan, just sprinkle here and there some (half/done/slow/wired/bridge) interfaces leads anyone, who tried to migrate, stuck as well. Some all ready started to migrate back ...

Here are two great articles that explore some Go footguns:

  * Lies we tell ourselves to keep using Golang [0]
  * I Want Off Mr. Golang's Wild Ride [1]

By the great fasterthanli.me

[0] https://news.ycombinator.com/item?id=31205072

[1] https://news.ycombinator.com/item?id=22443363

"Great" is far fetch especially "you shouldn't use Go for production services", which does not make any sense, also the same author works for a compagny that uses Go in places, which is kind of funny.