WebAssembly is a true write-once-run-anywhere experience.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

WebAssembly (WASM) is poised to replace containers like Docker by offering a true write-once-run-anywhere experience. Though currently limited by the lack of system interfaces like file access and networking, future integrations are expected. WASM offers the combined benefits of microservices and monoliths, particularly in serverless platforms such as Cloudflare Workers. Its adoption is growing, and developers are encouraged to become familiar with compiled languages like Go or Rust to prepare for its future dominance.

WASM will replace containers

Bold statement. I doubt it’ll be gone.
Unfortunately WASM isn’t going to fit all use cases, e.g. when you depend on external binaries that you invoke.
However, I think WASM can be a nice addition to the Kubernetes landscape with tools like <a href="https://www.spinkube.dev/" target="_blank" rel="noopener nofollow">SpinKube</a> that lets you run WASM in Kubernetes instead of containers. So instead of the kube-scheduler starting a container, it starts the WASM binary instead.

while it is true that java in the browser is not a thing anymore, it is still a “thing” everywhere else, especially in containers. not outside. so if we put the “true” compile-once-run-anywhere argument aside, i don’t see why wasm should thrieve outside containers while java bytecode should not?

I’ve read that the future will be no more UI app, but something like micro &amp; AI.
So if it is true, it can’t be the web
Want to see which will subsist

WASM is no different than Flash, Silverlight, JavaFX or even Java/.net runtime. The only difference is that there is no UI. It’s not a novel thing by any measure.
And why in the hell someone will use a virtual machine to run bytecode instead of using a database written in a native language? In some years, a 10Ghz machine with 256Gb of RAM would not even run notepad because everything is sooooo slow by those nonsense.
WASM should be a “compiled javascript”, because that one sucks a lot. It should NOT be a one-fit-for-all-solution (because it is a very poor one).

With this in mind chrome books are the future