If you’re worried about securing server side resources by hardening the client side, you’re doing something wrong. At any rate, the example you give is arguabl

If you’re worried about securing server side resources by hardening the client side, you’re doing something wrong. At any rate, the example you give is arguably a better case than what we have right now with JS — anyone interested in subverting client side access policies can poke around trivially in the JS globals, they don’t even need to decompile anything, they have a DOM inspector and a REPL to make exploits that much easier to pull off. If security through obscurity is your thing, compiling to WASM could only help. Again, though, client side shenanigans shouldn’t be of any concern anyway. Edit: I thought I was replying to the other comment you made within the context of client side execution, but I can touch on that too. Programming errors (and resulting exploits) aren’t something unique to WASM, and there’s nothing stopping you from using something like Go or Haskell or Rust as a source language, if you want something more safe than C.