Skip to content

Comment on WebAssembly adoption: Is slow and steady winning the race?

Comments

The assumption is that javascript is bad and that the solution is to not fix it. asm.js was another example.

asm.js was the opposite of an alternative to JavaScript: It was a performant JavaScript dialect used as a compilation target for various languages otherwise targeting emscripten.

WASM is the spiritual successor to that, getting rid of the (in retrospect quite hilarious) "embedded backwards compatibility layer".

You don't compile to js because js is slow.

edit: for the record, I think having only one doc type (html) and only one scripting language (js) in the browser is a terrible idea.

I don't know what the other doc types and programming languages should be but performance alone seems like a poor idea. A compile target seems even worse. :)

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.