4 ms·
Speed nowadays is almost an anti-goal. People choose the "fastest" language or framework, then add a bunch of lazy ORM queries without really knowing how to pr
by papito 4y ago
Speed nowadays is almost an anti-goal.
People choose the "fastest" language or framework, then add a bunch of lazy ORM queries without really knowing how to properly leverage a performant database, stitch together a bunch of "microservices", adding multiple HTTP trips across the wire, and by that time the performance of the core language is a rounding error.
- makeitdouble 4y agoTo note, nowadays node is not just for production runtime. Anything related to tooling (compilation/check/bundling etc.) for instance will benefit from faster runtimes. Also, having a slower runtime only marginally push people to code more efficiently (e.g. people wanting to use an ORM will do so either way)
- lpapez 4y agoI got a PHP gig recently (after working as a Go developer for some time), and this rings very true to me. In PHP you often have to make the most of your database, and this tends to result in a far more enjoyable codebase experience.
- nickserv 4y agoSure, until you're stuck on some inner loop with a poorly performing language. Of course,if you're doing microservices correctly, it should be easy to separate the parts where performance is important and write them in a language optimized for that.
- papito 4y agoThat is almost never used correctly. I have not seen it, for one. If it's crazy math calculations, file processing, image processing - sure, but that's not how microservices are used in 99% of the cases. It's basically an anti-pattern.
- crabmusket 4y agoAre you saying that performance can't be outsourced?