Slashdot Mirror

← Back to Stories (view on slashdot.org)

Google Dropping Netscape Plugin API Support In Chrome/Blink

Posted by ryuzaki0 on from the wither-portability dept.

An anonymous reader writes "Google today announced it is dropping Netscape Plugin Application Programming Interface support in Chrome. The company will be phasing out support over the coming year, starting with blocking webpage-instantiated plugins in January 2014. Google has looked at anonymous Chrome usage data and estimates that just six NPAPI plug-ins were used by more than 5 percent of users in the last month. To 'avoid disruption' (read: attempt to minimize the confusion) for users, Google will temporarily whitelist the most popular NPAPI plugins: Silverlight, Unity, Google Earth, Google Talk, and Facebook Video." Google offers NaCl as an alternative, and "Moving forward, our goal is to evolve the standards-based web platform to cover the use cases once served by NPAPI."

3 of 170 comments (clear)

  1. Re:"standards-based web platform" by XanC · · Score: 4, Insightful

    That may be, but why don't we "evolve" this other thing to cover all the existing use cases BEFORE disabling NPAPI?

  2. Re:If not NaCl or JS, then what? by RamiKro · · Score: 4, Insightful

    Yes. I am against both. Cross platform programming as an Interpreter running in a sandbox (JavaScript) or a bytecode VM (Java, NaCl...) shouldn't be done through the browser.
    The Internet should be slightly expanded HTML1 and CGI as far as I'm concerned. Maybe with an exception for audio\video if we can agree on a codec...

    Keep application development and serving to the likes of Android's Play Store + Dalvik.

  3. Re:If not NaCl or JS, then what? by LordLimecat · · Score: 4, Insightful

    Nothing stops you from only writing a webpage thats HTML1 with no JS; just dont be surprised when noone wants to visit it.