3 ms·
>And in these cases, time to market, speed of refactors and maintainability is much more important than the row speed (which again, may not even be that signifi
by DeathArrow 5y ago
>And in these cases, time to market, speed of refactors and maintainability is much more important than the row speed (which again, may not even be that significant at all. Eg, often most work is done on the db side)
About the raw speed. Maybe you want to take a look at these nice benchmarks? https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/
You don't have to ditch Java or C# for your app and use C or Rust instead. But you can write Java and C# in a more performant way while not sacrificing time to market, speed of refactors and maintainability.
Also, if performance, throughput, stability wouldn't be a thing, we have to wonder why Twitter switched from RoR to Java? Couldn't they just buy more servers instead?
- pkolaczk 5y ago> But you can write Java and C# in a more performant way while not sacrificing time to market, speed of refactors and maintainability. Writing Java in a more performant way often means ditching OOP and using primitive types, primitive arrays everywhere instead, and also avoiding allocations up to the point where all objects are reused. Such code is just as slow to write and as error-prone as C, and way worse than C++ where at least you have RAII, generics, STL algorithms and zero-cost abstractions.
- kaba0 5y agoYou only have to do that in hot loops (in most problems), that you can easily profile with the very good observability tools that java provides. The rest can be maintainable, good quality OOP code. I would even go as far and say that OOP’s encapsulation pretty much exists just for this: the “ugly” implementation can reside inside a class and you only have to care about its public API from the outside.
- 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.