4 ms·
> if WASM existed back in 2008, he wouldn't have created Docker! doubt it as there was JVM back then. >This is why I'd love WASM to win. Right now your browse
by trhway 5y ago
> if WASM existed back in 2008, he wouldn't have created Docker!
doubt it as there was JVM back then.
>This is why I'd love WASM to win. Right now your browser can run 100s of tabs, with inter-tab communications and all the security sophistications on a single machine.
Now just add K8s on top to orchestrate it :) Somebody will just develop new WASM based container ...
- pjmlp 5y agoAh, but WASM is Java for the haters, so it sells much better at the bytecode shop.
- jason0597 5y agoI wonder why the Java haters chose WASM over Kotlin
- ptx 5y agoKotlin for WASM is in the works[1], so once that arrives they won't have to choose between them. [1] https://www.youtube.com/watch?v=-pqz9sKXatw https://www.youtube.com/watch?v=-pqz9sKXatw
- immibis 5y ago"I wonder why the C++ haters chose ARM over Go" is a comparable sentence. I hope the error is clear.
- jason0597 5y agoI don't think so. The parent said: >[...] WASM is Java for the haters, so it sells much better at the bytecode shop. Which means WASM was advertised as a new bytecode VM to replace Java. What I'm saying is that, for these supposed Java haters, why did they choose to completely reinvent the bytecode VM when they could have just chosen Kotlin and not have to reinvent the wheel? It would fix most if not all of their concerns about Java.
- postalrat 5y agoIs the JVM made to be isolated like WASM is?
- phendrenad2 5y agoYou just use the Java standard library to do everything, and the Java runtime handles keeping them namespaced. At some point (right around the dot-com crash) everyone switched away from Java (because Python was free) and that resulted in using POSIX to do everything. No more namespacing. Then people wanted to scale, and, viola! Docker.