3 ms·
What made NPAPI something nobody is happy with has little to do with standardization approaches. Web APIs aren't a replacement for a plugin mechanism, and neve
by teacup50 11y ago
What made NPAPI something nobody is happy with has little to do with standardization approaches.
Web APIs aren't a replacement for a plugin mechanism, and never will be, because they live below the browser instead of as a peer of the browser.
Your dedication to a two-tier system of platform-level code access would be less hypocritical if you imposed the same restrictions on yourself -- but of course, if you did that, you couldn't actually ship a working, high-performing browser.
- pcwalton 11y ago> Web APIs aren't a replacement for a plugin mechanism, and never will be, because they live below the browser instead of as a peer of the browser. NPAPI is mostly below the browser nowadays. And PPAPI is completely "below the browser". In fact, that's its entire reason for existing. > Your dedication to a two-tier system of platform-level code access would be less hypocritical if you imposed the same restrictions on yourself -- but of course, if you did that, you couldn't actually ship a working, high-performing browser. I would love to implement more and more of the Web platform using the Web APIs, and there has been continuous motion in that direction for a long time.
- teacup50 11y agoContinuous motion, maybe. Continuous forward motion, not so much.