Hacker News Reader

I think people on this thread saying "any language would have worked" miss the point.

The solution was to find a simple, obvious to deploy and maintain and monitor piece of code, doing precisely the thing needed to solve the very specific problem they had, and nothing more.

And this is precisely the kind of culture that has been built around the go language from day one. So, in a way, it's absolutely not surprising that go was chosen.

View on HN

Finally somebody said it! You cannot divorce language from its engineering culture. Just compare how Go libraries and tools are made compared to Java. In the Java world everything is over-engineered to an extreme and if you as a new developer try to keep thing simple you will be quickly put in your place and told “that is not how proper Java programs are written.”

And Java is not alone in having that kind of engineering culture. You find it a lot of places but it is the community where I find it most noticeable.

Unfortunately Java seems to bleed its culture everywhere:

Modern PHP development seems to be about how much of a pyramid of class you can build to serve a single request.

Then you have all the new typescript frameworks, proudly inspired by Spring.

Maybe Kotlin will change this, given time.

Reply on news.ycombinator.com