Chrome Drops Java→

Oracle:

The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has been supported by all major web browsers for over a decade. Google’s Chrome version 45 (scheduled for release in September 2015) drops support for NPAPI, impacting plugins for Silverlight, Java, Facebook Video and other similar NPAPI based plugins.

I’m of mixed feelings about this – I dropped Chrome a little over a month ago, and I don’t actually have Java installed on at least one of my machines,1 but it’s still a very useful bit of software.
On the other hand, I can’t think of any2 use of Java in a web browser that wasn’t a downright painful experience. For some reason, people writing applets in Java take that as an excuse to ignore every convention of user interface design and instead make a piece of garbage UI.3


  1. Including virtual machines, at least. 
  2. Other than Minecraft Classic, which I believe is no longer available online. 
  3. This goes out to the ‘cash register’ UI, written in Java, that I had to use recently – a pile of crap that had two conflicting ways to do everything, neither of which made sense.