undefined

points

[-]

I don’t agree with this. If you found your favorite type of car, then that’s your preference. Each car can take you to roughly same place (unless you have a specific use case like off-road). If you a preference for a language, but your use case needs another language, then use case trumps preference. It’s silly to belittle a language preference given the facts.

Some languages and ecosystems are delightful to work with and people absolutely make reasonable trade offs to stay in them.

by moomoo115 days ago|

parent|

[-]

That’s not what I said at all in relation to the OP.

You and I agree. We are discussing people who don’t understand this nuance. That’s the majority of people I’ve met.

That’s why i said we use a hammer for a nail, and not a saw. Aka using the tool that makes sense.

by hshdhdhehd6 days ago|

prev|

[-]

Im i. the P95 perpetual mid levellers, but I also dont obsess about PL (but would avoid for example a PHP or VB6 job) but yeah Go, Node, C#, Java, python, whatever!

by amano-kenji6 days ago|

prev|

[-]

Initial speed matters, but sustainable speed matters as well. Your choice should be based on initial speed and sustainable speed.

Initial speed matters more, but sustainable speed can't be ignored.

by moomoo116 days ago|

parent|

[-]

Right, that's why I always suggest anyone doing "actual" product work to use something like node-TS and Go.

node-TS for insane developer productivity (hella libraries, who really gives a fuck about NPM issues? just patch and move on) and ability to scale easily (95% of CRUD IO workloads for most companies). Need computational horsepower? Use Go for that thing, compile binary, call binary from node..

Honestly, just that alone is able to scale to millions of users and is super easy to maintain (granted the code is architected well). 95% of companies aren't really doing anything crazy, and 99% of companies are not unicorns.