3 ms·

Google's announcement says > Once PNaCl is fully released, users will be able to run PNaCl modules on any web page – applications will not need to be deployed

by azakai 13y ago

Google's announcement says > Once PNaCl is fully released, users will be able to run PNaCl modules on any web page – applications will not need to be deployed through the Chrome Web Store in order to run PNaCl modules. NaCl has always been enabled only in the Store, and not on the web, while the news in that announcement is that it will be enabled on the web. If you still think that isn't clear, watch the recent Google IO PNaCl talk, where this is stated as well, http://www.youtube.com/watch?v=5RFjOec-TI0 http://www.youtube.com/watch?v=5RFjOec-TI0 If somehow there is a misunderstanding of the intent of both announcements, then I hope Google will clarify that.

munificent 13y ago
In case you're curious, the relevant bit is around here: http://www.youtube.com/watch?v=5RFjOec-TI0&feature=player_detailpage#t=2037s http://www.youtube.com/watch?v=5RFjOec-TI0&feature=playe.... "It's in Chrome 29 canary now, hopefully dev channel within a few days. We're shooting for Chrome 30 as our launch."
dragonwriter 13y ago
> NaCl has always been enabled only in the Store, and not on the web, while the news in that announcement is that it will be enabled on the web. ...when PNaCl is fully released. Which is what they've said for years, that they weren't turning any Native Client on for the web until PNaCl was ready to be "fully released". So that wasn't actually the news. The actual news was the announcement that PNaCl execution is supported (not that PNaCl will be "fully released") from Chrome 29, which was, at the time, the Canary version of Chrome (its since moved to the Dev channel.) Prior to Chrome 29, the only way to run PNaCl code -- or rather, code that had been generated by the PNaCl toolchain -- in the browser was to run it through another tool which generated regular, architecture-specific NaCl code.
- azakai 13y ago
  I understand it is possible to read those announcements in that way. It seems a bit of a stretch (look at how things are phrased in the video). But again, I hope you are right. There are plenty of Google people reading HN, hopefully they can quickly confirm things one way or the other.

by azakai 13y ago

munificent 13y ago

In case you're curious, the relevant bit is around here: http://www.youtube.com/watch?v=5RFjOec-TI0&feature=player_detailpage#t=2037s http://www.youtube.com/watch?v=5RFjOec-TI0&feature=playe.... "It's in Chrome 29 canary now, hopefully dev channel within a few days. We're shooting for Chrome 30 as our launch."

dragonwriter 13y ago

> NaCl has always been enabled only in the Store, and not on the web, while the news in that announcement is that it will be enabled on the web. ...when PNaCl is fully released. Which is what they've said for years, that they weren't turning any Native Client on for the web until PNaCl was ready to be "fully released". So that wasn't actually the news. The actual news was the announcement that PNaCl execution is supported (not that PNaCl will be "fully released") from Chrome 29, which was, at the time, the Canary version of Chrome (its since moved to the Dev channel.) Prior to Chrome 29, the only way to run PNaCl code -- or rather, code that had been generated by the PNaCl toolchain -- in the browser was to run it through another tool which generated regular, architecture-specific NaCl code.

azakai 13y ago
I understand it is possible to read those announcements in that way. It seems a bit of a stretch (look at how things are phrased in the video). But again, I hope you are right. There are plenty of Google people reading HN, hopefully they can quickly confirm things one way or the other.