Comment by igouy

> The Computer Language Benchmarks Game (it's terrible not only because it compares different algorithms, but also because it has no benchmarks that are long-running, none with interesting memory management, and no concurrent benchmarks - the very things most programs today do)

It also compares un-optimised single-thread #8 programs transliterated line-by-line from the same original.

However long (programs run) they never seem to become "long-running".

There's always some programmer who replaces "interesting memory management" with array and int.(Many complaints about Go binary-trees programs seemed to be: they should implement a custom arena.)

What does "no concurrent benchmarks" mean when:

    import java.util.concurrent.CyclicBarrier; 

> Of course, there aren't cross-language application benchmarks

Maybe something like

https://link.springer.com/article/10.1186/s12859-019-2903-5