> This is a big reason that I think wasm is a step in the wrong direction. It's basically nudging people into making things even more opaque.
WebAssembly is a tool, not a technique. It's not meant to replace JavaScript or the DOM, it's meant to supplement it in projects where it makes sense. Is it any more opaque than any other transpiled and minified SPA that in no way resembles anything remotely human readable anymore? I don't consider this a valid criticism of WASM.
> How, for example, would you go about blocking ads in this kind of app?
Probably the same way it's done now, by blocking requests to blacklisted domains known for hosting advertisements.
WebAssembly is a tool, not a technique. It's not meant to replace JavaScript or the DOM, it's meant to supplement it in projects where it makes sense. Is it any more opaque than any other transpiled and minified SPA that in no way resembles anything remotely human readable anymore? I don't consider this a valid criticism of WASM.
> How, for example, would you go about blocking ads in this kind of app?
Probably the same way it's done now, by blocking requests to blacklisted domains known for hosting advertisements.