https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
:and:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
Then you add multi-threading, and see a decent improvement, e.g. from 5 seconds to 1.5 seconds on 4 cores (almost all implementations show a similar gain)
And some languages with support for Vector operations further improves this to 0.7s
So this benchmark seems to be not very useful for comparing performance of any decent language. It could however be used for comparing improvements of using different techniques to solve the problem, or to showcase what new features brings to the table.
Saying "any decent language" assumes we know without measurement the very thing that we need to measure.
Showing "very similar performance characteristics" is a valid outcome.
So how different are the "busy" measurements?
To understand actual performance first understand what approaches were used.
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
How programs are written does matter.
What if we can all see implementations that are not wildly different?
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
But the argument here started as "Hey look language A is faster than language B" , while pointing out completely different implementations, which is, absurd.
danielscrubs referenced measurements which showed similar performance for Dart and NodeJS programs, but did not mention that similar performance.
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
The Dart implementation seems much slower than the NodeJs implementation and it doesn’t bring anything new to the table? It added null safety today.
Anyone that knows if it has any feature beyond for example what Ocaml has?