{"id":691,"date":"2019-11-30T18:40:57","date_gmt":"2019-11-30T22:40:57","guid":{"rendered":"https:\/\/jausoft.com\/blog\/?p=691"},"modified":"2019-11-30T18:53:29","modified_gmt":"2019-11-30T22:53:29","slug":"resurrecting-a-dying-species-bring-back-java-to-the-browser","status":"publish","type":"post","link":"https:\/\/jausoft.com\/blog\/2019\/11\/30\/resurrecting-a-dying-species-bring-back-java-to-the-browser\/","title":{"rendered":"Resurrecting a dying Species? Bring back Java\u2122 to the Browser?"},"content":{"rendered":"

While I was doing the admin work for the next JogAmp release 2.4.0<\/a> I added some old video teaser supporting the point of enabling high performance hardware accelerated features to anything Java\u2122’ish for any platforms.<\/p>\n

It rang some belts that all these demos were easily and interactive launched used Applets within the browser.
\nSadly today, browser don’t support such plugin’s anymore, which enabled simplified launching of Java\u2122 Applet’s and its seamless integration into the web page.<\/p>\n

I well remember the debates back then, about bloated browsers and security issues. But what do we have today? Bigger (or bloated) browsers containing the VM implementation itself, only that this time it is not Java\u2122 but a JavaScript VM. Not a big qualitative change, but a restriction to choice, IMHO. This move only disabled third parties enabling their content via the browser interface. Almost sounds like the old Microsoft and Firefox browser wars, only that this time all browser vendor are aligned and believe to be the good guys now \ud83d\ude09
\nMost notable for me is that the security issues has not changed here at all.<\/p>\n

So what can we do about it?<\/p>\n

There could be a potential path to resurrect my Applet3 showcase (git repository<\/a>) as demonstrated on Fosdem 2014 (see below), if we could resolve the following<\/p>\n