

See the main issue with that is you need to bundle everything into the app.
Modern computing is inherently cross-dependent on runtimes and shared libraries and whatnot, to save space. Why bundle the same 300MB runtime into five different apps when you can download it once and share it between the apps? Or even better, have a newer, backwards compatible version of the runtime installed and still be able to share it between apps.
With WASM you’re looking at bundling every single dependency, every single runtime, framework and whatnot, in the final binary. Which is fine for one-off small things, but when everything is built that way, you’re sacrificing tons of storage and bandwidth unnecessarily.






I have worked on games, and have a good understanding of the workflows involved.
You’ll obviously still need to do the creative parts manually (and should!) but the majority of the work involving the engine core build and the specific game coding, that can all be sped up borderline exponentially.
But I’m glad that someone with absolutely no understanding of the topic does their best to call out those who do show some experience on the topic just because they don’t get a neatly pre-chewed and pre-digested reply detailing all the information they lack and are unwilling to look it up themselves. As a next step would you like me to cut your steak up and feed it to you byte by byte, or tuck you in at night?