Ah, you mean client memory bloat, not transfer bloat (i.e. pageload time). That part was not very clear at all. You still need a nontrivial runtime (a la PNaC

Ah, you mean client memory bloat, not transfer bloat (i.e. pageload time). That part was not very clear at all. You still need a nontrivial runtime (a la PNaCl) if you're going to provide the sort of sandboxing guarantees for the code people want for code that runs without explicit user opt-in. Or is that a non-goal in your case? In that case, I'd like to understand the problem you're trying to solve, since it sounds different from the one JavaScript in web browsers is solving. I agree that things like asm.js have a performance hit compared to just running an unsafe binary blob. So does PNaCl (though the hit there is different from the asm.js hit: it has somewhat faster steady-state, but worse startup performance). Again, if you're not talking about something that has the same safety guarantees as JS and PNaCl you're comparing apples to oranges.