3 ms·
> I have no idea why Mozilla was so resistant to pnacl Pepper for one is a pretty good reason IMHO
by Raphael_Amiard 14y ago
> I have no idea why Mozilla was so resistant to pnacl
Pepper for one is a pretty good reason IMHO
- duaneb 14y agoWhy? It seems like a good replacement for npapi.
- sirn 14y agoBrendan Eich discussed about this few months ago at: https://news.ycombinator.com/item?id=4630334 https://news.ycombinator.com/item?id=4630334 Anyway, he said that the problem with Pepper is that its API is gigantic and its only spec is the implementation in Chromium. Other browsers could port the API but it come at very high cost due to WebKit-specific glue code.
- pekk 14y agoThe "problem" with pnacl is that it means the end of Javascript's death grip on the browser, which Brendan Eich is interested in extending for obvious reasons
- lukeschlather 14y agoI think you're overstating it. It more likely means the beginning of Google's death grip on the browser.
- munificent 14y agoHow does Google have a death grip on the browser?
- lukeschlather 14y agoThey don't yet. I'm saying pnacl is more likely to result in Google getting a death grip on the browser than ending Javascript's dominance.
- munificent 14y agoOooooh, the ominous "yet". Scary.
- jgraham 14y agoTo be clear, there are two things that have historically been called "pepper". The first was a basically a better version of NPAPI, with the limited scope that implies. That was replaced by something that's basically a Google-proprietary replacement for the entire web stack, with both the scope and the problems that implies.