Go has done what most programming languages aspire to: spark emotionally charged debates. Let’s walk through the arguments and see what’s really being said.
1. Go Is Boring, and That’s Not Good
The author laments Go’s simplicity, equating it with boredom. One has to wonder: is the author looking for a programming language or a theme park? It’s almost as if the lack of flashy syntax and endless ways to do the same thing (read: Java’s 75 ways to write a loop) has robbed them of the joy of feeling “clever.”
What really shines through here is a deep yearning for glue code—the kind that stitches together massive, overly abstracted frameworks where the “fun” lies in deciphering dependency trees and watching IDEs buckle under their own weight. The thing is, Go’s “boring” design is what makes it productive. One way to loop? Great! Let’s loop efficiently instead of philosophizing over whether we should map, reduce, or just throw a lambd