3 ms·
> Sure, but under the hood both the HTML5 APIs and Pepper APIs call into the same code It's still wasted effort, though. Maybe they share some code, but Pepper
by TazeTSchnitzel 12y ago
> Sure, but under the hood both the HTML5 APIs and Pepper APIs call into the same code
It's still wasted effort, though. Maybe they share some code, but Pepper is an unnecessary extra API. One that's non-standard and results in vendor lock-in.
- dman 12y agoDo you think Google could be persuaded to contribute PNaCL as an open standard?
- dragonwriter 12y agoJudging from their FAQ [0] on it, it doesn't seem like they are generally opposed to the idea, just see it as premature at this time. [0] https://developer.chrome.com/native-client/faq https://developer.chrome.com/native-client/faq
- pcwalton 12y agoThere were beginnings of talks to get cross-vendor consensus on Pepper (which would be a prerequisite to any standardization attempt of PNaCl) in 2010: https://mail.mozilla.org/pipermail/plugin-futures/2010-April/000088.html https://mail.mozilla.org/pipermail/plugin-futures/2010-April... The general consensus among non-Google browser vendors was that just using the existing browser APIs was a more desirable approach than Pepper. Since then, Pepper has remained a Chrome-specific technology.
- cpeterso 12y agoCould Google add NaCl support to Firefox with an add-on?
- TazeTSchnitzel 12y agoThey could, but why would they?
- dman 12y agoTo help developers?