Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Firefox is also favoring a phase-out of NPAPI usage, for largely the same reasons, though they are dragging it out longer.

Guess it'll be time to say Auto Updates -> Off.

Until the websites and services I use migrate to a different solution, if at all possible, I just will open myself up to vulnerabilities and security risks and stop updating at all.

I wonder how many users will do the same?

Maybe the browser companies will get lucky and the companies and services relying on this technology will simply fail since there is no alternative, and they won't have to deal with users holding out, since what they hold out for has been destroyed.



> until the websites and services I use migrate to a different solution

Any public websites or services you can reference? I legitimately can't think of a single website or service I use that will be impacted. Or are you talking more about like ancient internal systems written as a java applet?

> companies and services relying on [NPAPI] this technology will simply fail since there is no alternative

Any company that bet their business on NPAPI deserves to fail. The signals where clear since 2012 that this was coming, and was explicitly and directly stated since 2013. They had a lot of time to transition off.

A full decade ago I was helping companies transition off NPAPI because it was "legacy", "slow" and "buggy". I couldn't fathom a company being silly enough to develop a modern product using it.

Most of the "major" things dependent on NPAPI have fairly clear migration paths. Java Applet -> Java Web Start. Silverlight is entirely dead (despite MS supporting it out till 2021) and there are tons of migration paths off of it.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: