Hacker News Reader

Comment by teacup50 | Hacker News Reader

NaCL is open source, the papers and documentation are all open, the build tools are all open. The only thing it's not is standardized -- and that's not Google's fault.

Apple and MS are vested in their platform plays, and Mozilla has been playing a comparatively weak technical game for years.

View on HN

So basically it's a great solution except for the part where everybody else has misgivings about it. There are already standards covering almost everything from NaCl, and going by what it was supposedly for according to their original marketing campaign, 3D games, entirely supplanted already by current generation JS engines

It was a myopic stop-gap that's already starting to show its age, about the only thing it has left running for it is smaller distribution size and faster cold-start times, but they're implementation problems of current generation JS, rather than some fundamental benefit of NaCl

> implementation problems of current generation JS

Wake me up when you get to be end of the rainbow and find the pot of JavaScript gold supposedly waiting there.

Mozilla has been playing a comparatively weak technical game for years.

Except for the part where emscripten completely ate (P)NaCls lunch in a way that works cross-browser.

Uh, when did that happen? It's slow, it's complex, it's a terrible solution, it's barely seen any uptake and near zero interest from tool vendors.

Oh, and it's objectively, demonstrably inefficient. This is just another version of "I implemented something simple ... in JavaScript!". What lunch got eaten?

Zero uptake? It's a target for several important gaming engines now, which were an important target audience of NaCl.

There's really no point in replying to the rest of your (totally false) assertions.

Reply on news.ycombinator.com