Why? It seems like a good replacement for npapi.

sirn · on March 28, 2013

Brendan Eich discussed about this few months ago at: 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 · on March 28, 2013

The "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 · on March 28, 2013

I think you're overstating it. It more likely means the beginning of Google's death grip on the browser.

munificent · on March 28, 2013

How does Google have a death grip on the browser?

lukeschlather · on March 28, 2013

They 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 · on March 28, 2013

Oooooh, the ominous "yet". Scary.

jgraham · on March 28, 2013

To 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.