News for hackers. Stuff that matters.

A comment on Go: What We Got Right, What We Got Wrong. Parent comment

Re:Go: What We Got Right, What We Got Wrong by cryptos on Friday January 05, 2024 @02:35AM (#38876680)
Very true! I think a lot of the accidental complexity of early Java systems were rooted in the not so powerful language. If the language is too powerful (like Scala 2) developers do insane things with it. If the language is not powerful enough, developers create their own helpers and tricks everywhere and have to write a lot of additional code to do so.

Just compare Java streams with how collections are handled in Go and scratch your head how someone can come up with such a restricted language in this century.

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by groestl on Friday January 05, 2024 @02:56AM (#38876782)
> and have to write a lot of additional code to do so.

And most importantly: you have to read a lot of code like this, and understand it's assumptions, failure modes, runtime behavior and bugs, which are different every time. Instead of just reading "ConcurrentHashMap", and be done with your day.

[ Parent | on HN ]