4 ms·

> 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

> 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.

mattgreenrocks 3y ago
It’s also really gross how we want ultra prescriptive tools that force you to write things certain ways because we can’t trust our own coworkers to write decent code. Or learn things for that matter. I guess people don’t do code review at all? 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.
- uluyol 3y ago
  I'm sure this depends on engineering culture, but at Google, where Go was born, there is "one way to write C++" and that is dictated by the style guide. 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.
swader999 3y ago
It's more what you can afford to learn. Most of the domains I've worked in are so thick to grok that also loading in a programming language like scala or rust becomes intractable.
riku_iki 3y ago
experienced programmer often wants to learn just enough to take project from point A to point B as decided by business needs, and not spend nights of debugging cool stuff.
cyberpunk 3y ago
I've used scala and erlang professionally; I have nothing against learning new languages. 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....

mattgreenrocks 3y ago

It’s also really gross how we want ultra prescriptive tools that force you to write things certain ways because we can’t trust our own coworkers to write decent code. Or learn things for that matter. I guess people don’t do code review at all? 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.

uluyol 3y ago
I'm sure this depends on engineering culture, but at Google, where Go was born, there is "one way to write C++" and that is dictated by the style guide. 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.

swader999 3y ago

It's more what you can afford to learn. Most of the domains I've worked in are so thick to grok that also loading in a programming language like scala or rust becomes intractable.

riku_iki 3y ago

experienced programmer often wants to learn just enough to take project from point A to point B as decided by business needs, and not spend nights of debugging cool stuff.

cyberpunk 3y ago

I've used scala and erlang professionally; I have nothing against learning new languages. 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....