3 ms·
> you can write Java and C# in a more performant way while not sacrificing time to market, speed of refactors and maintainability. In practice you only have so
by lmm 5y ago
> you can write Java and C# in a more performant way while not sacrificing time to market, speed of refactors and maintainability.
In practice you only have so much attention and there are better places to spend it.
> Also, if performance, throughput, stability wouldn't be a thing, we have to wonder why Twitter switched from RoR to Java?
If raw speed matters we have to wonder why Twitter started with RoR, and only switched (mostly to Scala, not Java, AIUI) once they had tens of millions of users.
In a tiny handful of outlier cases where a given piece of code is run literally billions of times a day it eventually becomes worth doing performance microoptimisations. But only after you've confirmed that there's absolutely massive demand for this particular code and already done your iterative refactors and figured out what the code should do.