Hacker News Reader

There are two ways that a system can get unworkably complex. The most obvious is to overengineer and introduce too many excessively complex abstractions. However, it is equally harmful to become dogmatically obsessed with using the most "straightforward" implementation when more sophisticated approaches would make things easier to understand.

I have not used Go, but what I have heard makes it seem like it is designed in a way that would encourage the second approach.

That's the first thing anyone has ever said about Go that makes me want to learn the language. That sounds like an ideal programming language.

This mindset permeates through the entire ecosystem and tooling as well.

Enterprise projects build in single digit seconds, test suites fly by, project builds to a single binary (with embedded resources), most third party dependencies follow the established interfaces (which means plug and play) and so on.

It's the one language that I feel confident in, despite having worked in several other languages for many more years than Go.

I second this but I will say that the complexity demon lives in the reflect package.