3 ms·
Yeah, and V8, so we could just write JavaScript again and wouldn't have to deal with WASM. With a bit support from WASM and a few tweaks to V8 it could run near
by weinzierl 9y ago
Yeah, and V8, so we could just write JavaScript again and wouldn't have to deal with WASM. With a bit support from WASM and a few tweaks to V8 it could run near native JavaScript speed. Let's call it JavaScript paravirtualization.
- jfbastien 9y agoInterpreters can go a long way, but JIT code generation is required for really fast dynamic language implementation. That's quite a bit off for WebAssembly: https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#platform-independent-just-in-time-jit-compilation https://github.com/WebAssembly/design/blob/master/FutureFeat...
- dispo001 9y agoIf you strip out the legacy cruft it should be much faster. Reduce it to just the components used! If I understood properly: yes, I do share the bitterness. <troll> Look at us introduce this great new lang! It will potentially get rid of 99.99% of the current web developers and prevent any future script kiddies from getting in the game! Behold the speed of our sealed box environment little jimmy! Stay tuned for next weeks episode of Tech%20Elitism where we cover DRM for the web and public discourse policing!