Is the JVM made to be isolated like WASM is?
Re:WebAssembly: The New Kubernetes?
by phendrenad2 on Saturday January 22, 2022 @02:33AM
(#30034532)
You 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.
Ah, but WASM is Java for the haters, so it sells much better at the bytecode shop.
I wonder why the Java haters chose WASM over Kotlin
Kotlin for WASM is in the works[1], so once that arrives they won't have to choose between them.
"I wonder why the C++ haters chose ARM over Go" is a comparable sentence. I hope the error is clear.
I 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.
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 ...