Friday, April 24, 2015

End of Java?


Google Chrome's most recent release has been causing problems for people.  Specifically, if you use a site that uses Java (and many Courts do) the site will no longer work properly.  You may be redirected to Oracle's web site to download the latest version of Java.  However, updating Java will not help.

Google has decided that in its most recent release of Chrome (ver. 42) it will no longer support the NPAPI (Netscape Plugin Application Programming Interface).  As you might guess from its name, it was developed for Netscape Navigator 20 years ago.  It has been a very convenient way to run other applications through your browser Adobe Flash, Microsoft Silverlight (used by Netflix), and several other systems have used it as well.  Most of these other applications have complied with Google's demands to work with newer APIs, but Java has not.

As a result, Java will no longer work in Google Chrome.  There is a fix for this for now.  In Chrome, go to the following address:

chrome://flags/#enable-npapi

Click on the "enable" link.

This should re-enable the NPAPI, and Java will work once again.

However, this is a temporary fix.  Google has announced that with the release of Chrome version 45, which will probably be released in a few months, it will no longer offer the option to enable NPAPI at all. Once that happens, unless Java comes up with a new build, Java will not work in Chrome, period.

Microsoft has also announced that will no longer support the NPAPI in its new browser for Windows 10, although it offers limited support in Internet Explorer for the foreseeable future.  Mozilla Firefox also offers limited support.

Although this API has proven very useful over the years, it is being retired because it is a gaping security risk.  Hackers are using this to load malware on your computers from compromised web sites.  I understand why it is being retired and cannot understand way Java is resisting change.

During this transition, there may be other problems as well.  Essentially, web sites need to rebuild their sites to stop using Java or Java needs to come up with a fix to use more a more modern API.  As of today, Java has not announced that it is planning for a fix.

We, the end users, are stuck in the middle of this.  For now, I recommend using Internet Explorer if you have a problem getting to a site in Chrome.  If there is more new on this, I will let everyone know.

If you care to read more about this issue, this Tech Republic Article is quite informative.


No comments:

Post a Comment