> Performance is good enough, it's not the intellectual masturbation of Scala or Rust.
As we know, any technology that would require experienced programmers to learn something is a crime against engineering.
As we know, any technology that would require experienced programmers to learn something is a crime against engineering.
This was tried before and it was called Java.
But there’s always an eager generation of naive programmers willing to believe the lie that this time is different.
You have to learn many restrictions, a number of which feel arbitrary/highly subjective, and follow that. Of course, the style guide evolves over time so it's not like legacy code is consistent with new code.
The end result is that I much prefer the Go way of having fewer options in the language, instead of having those options in the language but restricting them via policy.
My comment was not really meant as seriously as the commenters here are taking it (I really didn't mean to infer anything about users of those..) -- but I also sort of stand by it -- I spent lots of time in stupid meetings about language features when I used those languages that I would have rather avoided.
It's of course not the languages fault, and more likely a smell of an org problem at wherever it was I was working back then (201x's).
It's completely true that I don't know rust; I tried, and $dayjob does use it for some components but it seems to be really overloaded with syntax and symbols to me -- then again I'm a dinosaur who started on C and maybe I'm just getting old....