Re:What I suspect Google is up to with Native Client
by bad_user on Wednesday December 07, 2011 @02:16AM
(#3322896)
I think Microsoft refusing to support NaCl is one of the best things they did. For once they pulled their head out of their ass and thought about the benefits of an open web.
I'm seeing a lot of comments here in support for NaCl, so apparently people have forgotten (or never lived) the days of ActiveX. I am not buying the conspiracy theory bits of this article, I also regret waisting time reading it ; however that doesn't mean NaCl isn't a bad idea.
As a multi-vendor standard with an
open source implementation ...
Dude, seriously, don't you think these "vendors" had good reasons to dismiss NaCl?
Re:What I suspect Google is up to with Native Client
by modeless on Wednesday December 07, 2011 @02:23AM
(#3322908)
The whole point of NaCl is the sandbox that blocks access to Microsoft's Windows APIs. Adopting it wouldn't have benefited Microsoft at all. What Microsoft should have done is built the CLR into IE as a JavaScript alternative instead of bolting a crippled version on the side (in the form of Silverlight). They could have controlled the best Web development platform out there, but that opportunity is long gone.
Re:What I suspect Google is up to with Native Client
by petegrif on Wednesday December 07, 2011 @12:33AM
(#3322605)
Agreed.
And I still don't understand Mozilla's problem with NaCl. They argue that js is now nearly as fast as native. Well...even if that were true it ignores the fact that as you point out there is huge investment in legacy code that NaCl unlocks AND it ignores the fact that js makes it easy to copy what may be valuable IP.
Re:What I suspect Google is up to with Native Client
by bzbarsky on Wednesday December 07, 2011 @09:13AM
(#3323810)
Mozilla's problem with NaCl is that Mozilla believes in open access to the web for everyone, while NaCl at the moment is tied to particular hardware architectures. The two seem to be fundamentally incompatible.
If PNaCl ever happens, that might change the situation, maybe.
As far as legacy code, emscripten unlocks it as well. Not with the performance of NaCl (and unlikely to get there), but it has the benefit of running cross-browser right now and not forcing people onto particular hardware platforms.
And copying "valuable IP" out of an emscripten-compiled program is just as easy as copying it out of a binary, of course.
Re:What I suspect Google is up to with Native Client
by ootachi on Wednesday December 07, 2011 @10:31AM
(#3324155)
As for PNaCl, I think "LLVM IR is a compiler IR" sums it up nicely: http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-October/0437...
They could have leveraged all of this by buying in to NaCl and putting it into IE. Hard to see how Google says no, and once Microsoft has that level of commitment to the technology, they'd get a strong say in its evolution. As a multi-vendor standard with an open source implementation, NaCl could have gotten real traction, and suddenly every C++ developer inside Microsoft and working for their customers has a path to the web for existing code that's slightly more plausible than rewriting everything in JavaScript and hoping the VMs get faster without also killing your laptop's battery (unlikely, I think).