3 ms·
Go seems to reliably trigger language wars every time it's mentioned. It's a surprisingly divisive language. Go users seem to mostly be happy cranking stuff ou
by xyzzy123 6y ago
Go seems to reliably trigger language wars every time it's mentioned.
It's a surprisingly divisive language. Go users seem to mostly be happy cranking stuff out but a lot of people hate it.
No generics, a culture of "if err != nil", type system not powerful enough, libraries not pure enough, too verbose, etc.
- pjmlp 6y agoBecause it basically has a culture of driving to the bottom in language features. Sure I can code full applications in GW-BASIC or whatever programming language of similar age, and did, almost 40 years ago. It doesn't mean I enjoy doing them today, beyond some nostalgic weekend hobby. Then again, assuming that generics proposal doesn't end the same way as the error one, it won't be that bad. Go will finally feel like using CLU (from 1975).
- xyzzy123 6y agoI think of it as the new PHP. Early PHP was a terrible language that people nonetheless built a ton of cool things with, for a variety of ergonomic and social reasons that are not that easy to pin down exactly.
- nine_k 6y agoOne reason is that people with ideas and a drive to implement them are often not experienced developers. They have a product mentality, and see the need to implement things in code as a nuisance that stands between them and their idea. So they pick the easiest, lowest-hanging tool, not the sharpest or cleanest.
- fomine3 6y agoI'd like to say it's similar to old day's Java. PHP introduced random features early days but Java and Go doesn't.