2 ms·
WASM is just an intermediate representation / compilation target. It's not meant to be human readable or human writeable. You're right that today it could be d
by arcticbull 9y ago
WASM is just an intermediate representation / compilation target. It's not meant to be human readable or human writeable.
You're right that today it could be difficult to debug things that are compiled down to WASM as initially it was difficult to debug C code compiled to traditional assembly. The next step, though, was debuggers. These will come, and the issue will become moot.
tl;dr: The tooling will follow.
- paulhodge 9y agoEven after 10 years or so, when the tooling is good enough to match the debugging experience we have now, it won't be a moot issue. There will be a much more common problem where you want to examine/modify the source code for a site, and you can't, because that site only published the non-debug WASM. One of the things that keeps the web platform healthy is the way that client-side sources are pretty visible. In response to "But JS can be obfuscated/minified" - Minified JS is still much easier to examine/modify than WASM, and it's really rare for a site to deliberately obfuscate their JS beyond minification.