News for hackers. Stuff that matters.
Re:"Optimizations should be added to V8" for the asm.js subs... by duaneb on Thursday March 28, 2013 @05:32AM (#5453941)
Why? It seems like a good replacement for npapi.
Re:"Optimizations should be added to V8" for the asm.js subs... by sirn on Thursday March 28, 2013 @05:37AM (#5453954)
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.

Re:"Optimizations should be added to V8" for the asm.js subs... by pekk on Thursday March 28, 2013 @08:27AM (#5454376)
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
Re:"Optimizations should be added to V8" for the asm.js subs... by lukeschlather on Thursday March 28, 2013 @12:19PM (#5455741)
I think you're overstating it. It more likely means the beginning of Google's death grip on the browser.
Re:"Optimizations should be added to V8" for the asm.js subs... by munificent on Thursday March 28, 2013 @01:58PM (#5456493)
How does Google have a death grip on the browser?
Re:"Optimizations should be added to V8" for the asm.js subs... by lukeschlather on Thursday March 28, 2013 @02:13PM (#5456597)
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.
Re:"Optimizations should be added to V8" for the asm.js subs... by munificent on Thursday March 28, 2013 @04:16PM (#5457336)
Oooooh, the ominous "yet". Scary.
Re:"Optimizations should be added to V8" for the asm.js subs... by jgraham on Thursday March 28, 2013 @07:34AM (#5454239)
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.