Google Dropping Netscape Plugin API Support In Chrome/Blink
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."
Standards are wonderful, and everyone should have their very own!
The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
I use the AmazonMP3Downloader plugin so when I purchase music from Amazon it gets added to my music library immediately.
AFAIK PPAPI (and NaCl) can't implement that because they need to save the music to places outside the sandbox.
Maybe Google can help define a "download to music library" HTML5 API?
NaCl is a good implementation of a terrible idea: i.e Running software in the browser is all kinds of wrong.
NaCl is "running software in the browser". JavaScript is likewise "running software in the browser", so it appears you'd be against that too. Would you rather require every developer of an Internet-connected application to develop an app for Windows, develop an app for Windows RT, develop an app for OS X, develop an app for GNU/Linux, develop an app for iOS, develop an app for Android, develop an app for Windows Phone, develop an app for Wii U, develop an app for Nintendo 3DS, develop an app for PlayStation 3, develop an app for PlayStation Vita, and develop an app for Xbox 360?
That's why I don't use chrome. But firefox probably does the same.
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
...can also offer pepper. Seriously, this is crazy. Everyone knows Google won't do no evil.
Time is what keeps everything from happening all at once.
I use the AmazonMP3Downloader plugin so when I purchase music from Amazon it gets added to my music library immediately.
AFAIK PPAPI (and NaCl) can't implement that because they need to save the music to places outside the sandbox.
AmazonMP3Downloader could be split into a part that runs inside Chrome and a separate process that downloads the file, and the two parts would communicate with Chrome native messaging. It's like when Windows Vista came out: applications that needed to run in the background with administrative privileges needed to be split into an elevated service and a not-elevated GUI.
Mark my words: Chrome is going to end up being a second IE 6-like millstone around the IT industrys neck. We are already seeing web sites that only work in Chrome (and Safari, if you're lucky). Firefox, IE (!), and whichever intrepid fourth party browser engines still exist on the periphery, will be reduced to second-class citizens..
More and more Chrome is reminding me of IE from the humble IE 4 which was the best browser to the jaguarnut of IE 6 which still has not completely died off yet in China and some corporate portals.
Chrome rushes to throw HTML 5 and CSS 3 features not standardized on W3C so they can pass HTML5test and calls them HTML 5 and CSS 3 but really are made just like box model and CSS were invented by IE. The W3C in the end decided to make it a little different which is why when Firefox went one way the corps hung onto IE 6 instead.
This NACL and plugins is all 21st activeX to me. If MS did this for IE 11 everyone would be screaming bloody murder.
http://saveie6.com/
I simply cannot function without that browser add-on. Why is Google doing this? I will be forced to switch browsers. :(
I find it telling that even Google Earth doesn't use NaCl yet.
I do not fail; I succeed at finding out what does not work.
If Google is so concerned with serving up cross platform applications, they can package a VM and an App Store along with their browser.
Chrome Web Store already exists on desktop versions of Chrome.
The Internet should be slightly expanded HTML1 and CGI as far as I'm concerned.
Usability would be horrible. For example, web-based paint programs can currently use HTML5 Canvas, SWF, or Java. But without any sort of client-side scripting, they would have to use a server-side image map and make a round-trip for each click on the image. And imagine how much longer Slashdot comment pages would take to update if every time you expanded or collapsed a comment, the server had to resend the full text of all other comments.
Quake Live runs their engine through a NPAPI plugin. They're supposed to port that to NaCl just for Chrome users? More likely they'll just not support it and ask people to switch to Firefox.
Google once again shuts down a service/feature, but this time they have the audacity to rub NaCl in the wound. That burns, it really does.
Silence is a state of mime.
I used to have a programming job which involved maintaining a large C++ codebase which was shipped as a Windows desktop app, a Mac desktop app, NPAPI plugins on both Windows and Mac, and an Active X control. As it was written before 'modern' Mac NPAPI, you can imagine how ridiculously convoluted it was converting the Mac plugin to support such necessities as Core Animation layer rendering, and the sandboxed event handling that Safari moved to as an attempt to make NPAPI plugins secure. So I spent literally years trying to keep that sinking boat afloat when it was obvious we needed a Javascript/web app replacement product.
"I know, we'll just throw away 5% of our installed users."
You would have thought that Google would have heard of the long tail...
It's not a standard just because you publish the documentation. Or can I make the Hugo-Plugin-Standard now?
Google is just being a bully because of it's position. "Adopt our made-up standards, or don't interact with us."
I think it's the "many people would give up their civil rights for a pint of beer" problem. We use Google products because they are nice and get the job done. Same reason why people use Facebook despite the datamining. Same reason why people get games from Steam despite the DRM. It's not a good thing, but I believe this is the reason. You don't feel the wrath of the evil parts in the typical day-to-day user experience.
This is going to make the VMWare browser-based console not functional, which was the only way to manage your VMWare instances in linux.... super.
How do you think MS was able to fast track Office XML into an ISO standard?
Some "standards" don't happen without force.
Democracy Now! - uncensored, anti-establishment news
Manufacturer of what?
Manufacturer of the computer. Mostly I was trying to exclude PowerPC Macs from a discussion of the future direction of NPAPI.
amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
Now let me rephrase my question: For which of these platforms are NPAPI plug-ins still released?
Scanner support for is on my short list of things to implement in Firefox, along with webcrypto so that sites stop using Java for its crypto library. I'd love help with it for anyone who is interested.
Why would running code in a browser create a huger security risk than running code outside of a browser?
because the god damn browser wasn't expected or designed to run code originally
Expecting the current version of a computer program to be no larger in scope than the first version is a form of the appeal to tradition fallacy.