News for hackers. Stuff that matters.
Re:Portable Native Client by pvnick on Tuesday November 12, 2013 @04:20PM (#6721210)
I agree, that's the thought I've had ever since learning of native client. These native, proprietary solutions have come and gone, such will be the fate of NaCl. As far as I'm concerned the future of high-performance webbrowser computing will be javascript-based through projects like asm.js or remote cloud architectures (eg https://brendaneich.com/2013/05/today-i-saw-the-future/)
Re:Portable Native Client by axelf on Tuesday November 12, 2013 @04:46PM (#6721426)
How is this proprietary? Isnt there an open spec?
Re:Portable Native Client by bzbarsky on Tuesday November 12, 2013 @08:30PM (#6722749)
For Pepper? There is not, in fact. There's some developer documentation, but nothing resembling an actual implementation spec.
Re:Portable Native Client by azakai on Tuesday November 12, 2013 @04:59PM (#6721531)
The code is open source, but last I heard there isn't a spec for PNaCl/PPAPI.
Re:Portable Native Client by eliben on Tuesday November 12, 2013 @06:41PM (#6722260)
The PNaCl ABI is defined here: https://developers.google.com/native-client/dev/reference/pn... - and it's definitely a work in progress we'll be trying to improve. As for Pepper, it's also all documented here and below - https://developers.google.com/native-client/dev/pepperc/

Granted, this is documentation, not a standards-body spec.

Re:Portable Native Client by azakai on Tuesday November 12, 2013 @07:00PM (#6722353)
Yes, certainly has had effort put into proper documentation. Do you know if there is also work being done to spec it formally?
Re:Portable Native Client by eliben on Wednesday November 13, 2013 @12:43PM (#6726876)
We're definitely considering it.
Re:Portable Native Client by cpeterso on Tuesday November 12, 2013 @04:49PM (#6721449)
Is there a PNaCl spec or just Google's implementation?
Re:Portable Native Client by ahomescu1 on Tuesday November 12, 2013 @06:44PM (#6722276)