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.
I 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.
To 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)
Sure, 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.
That 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.
Yes, I had to backtrack while parsing this sentence. Not all-capitalized would not have helped, "will" is still the first word, so would get capitalized regardless, and Bun is a proper name that would also get capitalized. It doesn't help that "bun" is a kind of bread, and is also part of the name of the "bo bun" dish.
An aside, but as a non-native speaker and haven't heard of Bun before, an all-capitalized title is very confusing. "Who is Will Bun"?