It promises to neutralize the playing field like Java promised, and Docker.
I’ve seen WASM do some cool shit, don’t count it out. Just factor in the irrational exuberance.
In addition with so many compile to JS technologies and chains, WASM is sort of another choice. Not a big deal for a team to choose it.
I don’t know enough about will it replace docker. But a lot of docker use cases are a bit of a leaky abstraction over what you are trying to achieve. For example why do I need to know what Alpine Linux is in order to run a node app? OK there is a node image that hides this detail but barely, you end up having to think about this sort of stuff.
Does it have the marketshare to make AWS make significantly different decisions? Remains to be seen. I guess people paid money for serverless. Could go that way
Edit: I never thought node.js would take over half of the information sphere, so read me more like a graybeard who is too young to be one.
In case you need to install anything in it as well as your application.
> Unfortunately, one of the challenges of running Docker on macOS or Windows is that these Linux primitives are unavailable. Docker Desktop goes to great lengths to emulate them without modifying the user experience of running containers. It runs a (light) Linux VM to host the Docker daemon with additional "glue" helpers to connect the Docker client, running on the host, to that VM.
https://mirage.io/blog/2022-04-06.vpnkit
WASM and WASI would actually be a cross compatibility story because you could compile to an architecture and syscall interface that is platform agnostic.
The issue is that I cannot easily compile.