2 ms·
It seemed inevitable that a new language would choose WASM as a runtime. We get a bytecode runtime to rival JVM and CLR, but with a diversity of stake holders
by solarkraft 3y ago
It seemed inevitable that a new language would choose WASM as a runtime.
We get a bytecode runtime to rival JVM and CLR, but with a diversity of stake holders (no single vendor trying to push a language or enterprise offering), it's JITed even on Apple devices and on the damn web! Pretty amazing.
What makes me excited about this: Getting to poke around, at runtime, my compiled .NET C# code using PowerShell (in Snoop) was pretty eye-opening to me. The "standard" interoperability between PowerShell (Core?) and .NET objects as well, of course.
It feels great to have a common runtime making calling out to other languages so seamless. Yet it seems to me like it never reached the popularity it deserved, but maybe it will get another try, with a lot more enthusiasm (no more Oracle/MS brake-foot).
- pjmlp 3y agoExcept the detail that it is mostly driven by Google, given Chrome's market share.
- nolist_policy 3y agoWrong, Google drove NaCl for a long time (portable LLVM bytecode) but then Mozilla countered with asm.js which kickstarted and heavily influenced the development of Webassembly.
- pjmlp 3y agoWrong, because you are only focusing on what lead to WebAssembly 1.0, almost a decade ago, not what happened afterwards the Web turned into ChromeOS.