Correcto is OpenJDK with Amazon branding, I left it out on purpose.
Still, a dynamic language winning out a strongly typed one, only for those that don't have a clue about how compilers work, or how to write winning micro benchmarks.
While still far from perfect, benchmarks comparing actual, practical usage, like the ammount of request served by webservers for example, are much better indicators imo.
Yeah everyone says that and stops there which is absolutely useless. Benchmarks are at least objective ways to measure something. And there are no "correct" benchmarks. Unless you have better metrics or another way to prove things, please stop repeating these meaningless words
I've literally pasted benchmarks measuring actual job (webserver request per second) in a comment below.
But besides, the critique isn't meaningless even without providing a better one;
If your benchmark is measuring things that are trivial no matter the language (like stack-based operations), but ignores things that actually differ meaningfully (like handling of heap objects), then criticizing such aproach is perfectly fair and valid objection
These benchmarks include startup time _and_ processing time when comparing languages. I don’t believe that is telling a very compelling story given JS is still slightly slower than most of the Java metrics unless you are looking for a new language to write your lambdas.
I only see random Java in synthetic benchmarks, without testing all variations of JIT and AOT compilers available throughout the ecosystem.
OpenJDK, GraalVM, OpenJ9, Azul, PTC, Aicas, ART, JikesRVM,....
Not to mention the optimizations that a dynamic language like JavaScript will never be able to take advantage of.
?
openjdk, GraalVM, Corretto
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
Correcto is OpenJDK with Amazon branding, I left it out on purpose.
Still, a dynamic language winning out a strongly typed one, only for those that don't have a clue about how compilers work, or how to write winning micro benchmarks.
Synthetic benchmarks for some algorithms have little to do with actual performance of real life applications
What method do you propose to compare the performance of different programming languages?
While still far from perfect, benchmarks comparing actual, practical usage, like the ammount of request served by webservers for example, are much better indicators imo.
https://web-frameworks-benchmark.netlify.app/result
[dead]
Yeah everyone says that and stops there which is absolutely useless. Benchmarks are at least objective ways to measure something. And there are no "correct" benchmarks. Unless you have better metrics or another way to prove things, please stop repeating these meaningless words
I've literally pasted benchmarks measuring actual job (webserver request per second) in a comment below.
But besides, the critique isn't meaningless even without providing a better one; If your benchmark is measuring things that are trivial no matter the language (like stack-based operations), but ignores things that actually differ meaningfully (like handling of heap objects), then criticizing such aproach is perfectly fair and valid objection
These benchmarks include startup time _and_ processing time when comparing languages. I don’t believe that is telling a very compelling story given JS is still slightly slower than most of the Java metrics unless you are looking for a new language to write your lambdas.