alt Hacker News1) Wasm wouldn't prevent you from running those client scripts (e.g. remove fixed elements). That would still just be a script that modifies the DOM from an extension after the page is rendered/dom mutations occur.
2) wasm makes serving static content practical as server side rendering is economical. My previous employer, for instance, spends tens of millions of dollars every year running SSR servers - almost all of that would be eliminated if the backend could just run the client as wasm.
3) Scrapers (think puppeteer) would be faster and more resource efficient because they wouldn't need to start a JavaScript runtime to load a page.
4) You don't use Electron apps?
5) You may not, but everyone else uses rich interactive web applications. Think of the energy usage and cost savings there would be to the world.
>You don't use Electron apps?
I've tentatively concluded the I should stay away from them for security reasons. That is what the Secureblue project recommends. I like vscode, but have no current need for it, so I did not install it the last time I installed an OS. If I ever start coding full time, I'd need something vscode-like and would try to make do with Github Codespaces. I've already made sure Codespaces runs in my browser (Trivalent with wasm, webgl and webgpu disabled) and have found a way to use it without a browser's tab bar and location bar taking up valuable screen real estate.