I don't think PNaCl guarantees timing determinism. Not sure what you mean by "code signing" in this context. The API attack surface is a non-issue; it's alrea

I don't think PNaCl guarantees timing determinism. Not sure what you mean by "code signing" in this context. The API attack surface is a non-issue; it's already accessible by any page that serves a PNaCl object. There's a small performance deficit but it's getting smaller. AOT compilation and caching of compilation results is possible; asm.js did it. I already mentioned shared-memory parallelism (it's just about done); did you read what I wrote? Standard cross-browser Web APIs give you access to those devices already. Same-origin is a strait-jacket --- a necessary one. "Break the Web's security model" isn't a desirable feature. "Elegance" is just a point of view. From another point of view, "duplicate everything in the Web platform" is not elegant. As for maturity and bugs --- having multiple interoperating implementations and real specifications is a good way to drive competition on quality ... and to distinguish "this is a bug, fix it" from "hello de-facto standard!"