2 ms·
> The point is that Google isn't self-motivated enough to get an Open-PNaCl-Whatever in shape to be standardizable on their own. They need Moz and Opera to push
by azakai 15y ago
> The point is that Google isn't self-motivated enough to get an Open-PNaCl-Whatever in shape to be standardizable on their own. They need Moz and Opera to push them, not rebuke them.
Opera, Mozilla, Microsoft and Apple can't help Google push a standard that doesn't make sense for the web. I don't understand what you want them to do. Help from the other browser vendors can't magically fix the problems already mentioned with NaCl.
The only thing they can do, is ignore the principles of standardization and what is good for the web, and just drop NaCl into their browsers. That would be terrible though.
> Meanwhile, Alchemy and NaCl can deliver a better-than-iPad3 user experience (zero install + sandboxed, etc) comparable to http://infinitybladegame.com/ http://infinitybladegame.com/ to the browser today.
http://dl.dropbox.com/u/6873971/data/cube2/index.html http://dl.dropbox.com/u/6873971/data/cube2/index.html
And again, this is before actually optimizing for that kind of code. In a few months that will improve even more.
> When I speak of deeply-optimized native, I'm talking about large volumes of tuned double-precision SSE vs tuned double-precision math in JS.
That's true, for that kind of code JS is slow currently. Things like RiverTrail should help, but they are not close to ready yet.
- corysama 15y agoWhat I want is to /eventually/ get PNaCl with WebGL/WebAudio/IndexDB/whatever APIs make Mozilla happy. I make high-end 3D apps to pay my bills. I want to bring them to the web. But, what I don't want is to go through Adobe's content approval process in order to not be 15 years behind the technology curve (Cube2=Quake2=1997). JS+WebGL is great and I'll keep pounding on it. But, building JS into the world's VM because of the asteroid-like inertia behind JS is frustrating in a similar way to watching Intel bolt stuff on to a pocket calculator CPU (8086) until we get a CoreI7. It obviously /can/ work, but...
- azakai 15y ago> What I want is to /eventually/ get PNaCl Well, NaCl is in no way a step towards that. They are completely separate technologies: One is a modified gcc compiler and custom validator in the browser, the other is a modified LLVM compiler and another modified LLVM compiler in the browser. The only similarity between them is the name, and some of the SFI approaches they utilize. But their code, potential spec for standardization some day, startup times, portability etc. are entirely different. Supporting NaCl now would not help out PNaCl in any way. (In fact, the opposite could be argued.) > But, building JS into the world's VM because of the asteroid-like inertia behind JS is frustrating in a similar way to watching Intel bolt stuff on to a pocket calculator CPU (8086) until we get a CoreI7. It obviously /can/ work, but... First thing, I do understand your frustration. I feel it too. But JS isn't just there because of inertia. There is no other valid option, all the proposals have major flaws, either technical or legal. JS also has its flaws, to be sure. But since the others are not clearly better (running faster, but only on certain CPUs is not better), JS will win because it does have inertia.