Oracle Says It Is Killing the Java Plugin

[tuqqer]

Breathe a sigh of relief?

http://gadgets.ndtv.com/apps/news/oracle...gin-795547

[Buck]

Good Riddance!

"Oracle acquired Sun Microsystems, and by extension the Java plugin, in 2010. The Java plugin, much like Adobe's Flash and Microsoft's Silverlight utilises NPAPI, an old Netscape Plugin API. Over the years, these plugins have caused more trouble than good. We have seen plenty of security attacks that used Java plugin as the target link.

Not everyone will be happy about the demise of Java, of course. Aside from developers, many enterprises are likely still running older Web browsers that need Java, and created plenty of applets for the same."

[cbelt3]

Most large scale corporate systems have moved away from client executable environments like Java, Flash, Silverlight, etc. ... in the main due to the inherent security risks. Unfortunately this puts a larger demand on bandwidth.

[M A V I C]

The Java plugin, much like Adobe's Flash and Microsoft's Silverlight utilises NPAPI, an old Netscape Plugin API. Over the years, these plugins have caused more trouble than good.

I'm sure that line sounded good to the author, but it's not even remotely accurate. The use of that plugin architecture got us to where we are today. Without it, websites wouldn't have nearly the capability they do now.

I am glad to see Flash, Java... plugins going away. But to say that entire plugin architecture caused more trouble than good is ridiculous.

Also, this line: Not everyone will be happy about the demise of Java

More craziness. The Java web browser plugin is going away, not Java. The author clearly doesn't understand the difference between the two. Java is NOT going away.

[Filliam H. Muffman]

I wonder if they did it because they were spending more money on fixing security holes than trying to advance the platform.

Yeah, Java still has a huge footprint behind the scenes at many large companies. Adobe isn't shutting down because Flash is a security risk, Oracle isn't shutting down because the Java plugin is in the same boat.

[mattkime]

>>I wonder if they did it because they were spending more money on fixing security holes than trying to advance the platform.

growth is in mobile. they needed a plan to go mobile or give up. they gave up.

[Z]

Java plugin MF'er was bugging me to update itself last night on the iMac!

[decay]

we have clients that rely on Java applets for logging into their time clock site at work. Hmmmm

[JoeH]

decay wrote:
we have clients that rely on Java applets for logging into their time clock site at work. Hmmmm

Kronos? We use that here, requires both Java and Flash in the recent version we just upgraded to last Summer.

[Sam3]

ADP requires the Java Plug-In as well. And what's worse, is the required Java tends to be a few generations old, and older for the manager approval version of ADP.