Hacker News new | ask | show | jobs
by datadeft 1105 days ago
> has near native performance

what do you mean by this?

https://github.com/niklas-heer/speed-comparison

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

3 comments

> speed-comparison

a tiny tiny ten-line snippet of code

https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

The second you remove threading and SIMD from those examples, they get rather close to JS. At most, you are making the argument that killing JS-SIMD for WASM and not adding native threading support was a mistake.
> The second you remove threading and SIMD

Anything else?

AsmJS coercion hints still work, so not really. Monomorphic code and some optimization can take you a surprisingly long way toward good performance. You certainly won’t find that in most untyped languages.
Much faster than Python or almost any non-native-compiled language (except Java)
Python is a notoriously slow language so that's not saying much.

And there are a number of languages on the JVM e.g. Java, Scala, Kotlin, Clojure as well as countless compiled ones which are near-native.

JVM languages do look interesting and with Graal there seems to be an evolutionary upgrade path from JavaScript code.
"Faster than Python" is a very different thing than "near native performance".