3 ms·
> it misses the point of the talk to suggest that wasm is the prediction bearing fruit Does it? It seems that the talk has two main points: 1. Javascript suc
by earenndil 8y ago
> it misses the point of the talk to suggest that wasm is the prediction bearing fruit
Does it? It seems that the talk has two main points:
1. Javascript succeeded because it was (at least initially) just good enough not to be completely unbearable, but bad enough that people ended up using it primarily as a target for other languages.
2. Ring 0 JIT can be 4% faster that normal binaries.
WASM is primarily a target for other languages, and qualifies as a language that can theoretically be JITted 4% faster than native code can be run.
- reitzensteinm 8y agoPoint number one isn't applicable to wasm. The execution inside the kernel is related, but nobody replies to a lua in kernel post with a link to the talk.
- pjmlp 8y agoBecause Lua isn't related to Web development, while JavaScript and WASM are.
- reitzensteinm 8y agoRight, but that's my point. Wasm is tenuously connected with JavaScript because both are web technologies, so people link the talk. But they couldn't be more different technically, and if wasm does indeed become the lingua franca of future computing it will be much more boring than the craziness of js doing the same. The talk was great because it was about an insane yet plausible future. We now have a boring and probable future.
- pjmlp 8y agoI don't believe in that, too much experience to believe in a miracle bytecode format that will magically succeeded where others failed. It will just be yet another VM platform.
- reitzensteinm 8y agoEven less reason to link to the talk then :-)