And they were given a 4 year heads up that chrome was going to remove it.
Instead Java used that time to build several help pages that showed you how to install other browsers then made a shitty anti-chrome campaign when it was finally removed, and unity just sat there and did nothing the whole time.
"I don't expect Chrome to keep supporting PPAPI native plugins for any longer then they have to (in order to support Flash), because it has the same security issues as NPAPI.
And, porting the plugin to PPAPI would be far from trivial, and not be compatible with existing content anyways"
Is any of that fundamentally wrong? They decided it was a better use of their time to go right to WebGL.
Honestly I'm not that sure, and that was a shitty way for me to word it about Unity. The big thing with PPAPI is that it can be much more sandboxed than NPAPI ever could, which means it already has a big step up in security, but obviously anything whose purpose is to circumvent the restrictions put in place for the browser is going to be inherently less secure than just running a website. In the end PPAPI could let you run code from a webpage as "root" on your computer, and there is nothing Chrome or anyone else can do to stop that.
That being said, I think Unity is going in the right direction trying to get away from plugins altogether. They are trying (successfully IMO) to compile to "true" web technologies and let the game be exported as HTML5 and javascript which is the right choice.
Instead Java used that time to build several help pages that showed you how to install other browsers then made a shitty anti-chrome campaign when it was finally removed, and unity just sat there and did nothing the whole time.