5 ms·

The answer to this question is almost certainly "no". It is ironic that what was originally the most hyped feature of Java has now been removed. But nobody is

The answer to this question is almost certainly "no". It is ironic that what was originally the most hyped feature of Java has now been removed. But nobody is going to miss it.

lucumo 5y ago
I worked on one this year. You need Java 8 for it and an insanely old browser. They didn't mention the applet part in the job description. That was my shortest tenure ever, including Summer jobs and internships...
- msgilligan 5y ago
  Ugh. Sounds horrible.
- vbezhenar 5y ago
  Some applets could be launched with javaws, but it would require some tinkering to extract proper jnlp file from HTML or JavaScript. I managed to do so with HP iLO remote KVM app.
  - marwis 5y ago
    javaws was also removed =)
    - vbezhenar 5y ago
      Need to use old Java, yep. Not as painful as using old browser.
tablespoon 5y ago
>> Tried running a Java applet recently? ;P > The answer to this question is almost certainly "no". For me, it's a yes. My employer uses some ancient monitoring application called SiteScope. They recently "upgraded" from an ancient version to a newer one (I think the latest), and nearly the whole frontend appears to be implemented as a Java Applet. Since no browser on the Mac supports Applets anymore, their workaround was to download some Java App that ran the UI. The older version we had used HTML.
- latchkey 5y ago
  I love the concept that the solution is to work around the applet issue and not find some new monitoring software. I wonder how effective ancient monitoring software is.
  - tablespoon 5y ago
    > I love the concept that the solution is to work around the applet issue and not find some new monitoring software. The workaround is actually part of the software itself (there are instructions right below the login box). My understanding is they're only upgrading because the old version didn't support modern versions of TLS, and there's a big push to get off of those. Finding new monitoring software would be probably be more work. At a minimum, the new version probably supports all the features we're using, and at best all our configuration can be automatically migrated. I don't know the details: I'm not part of the project, I just have an some apps with some monitors setup for them. > I wonder how effective ancient monitoring software is. It gets the job done.

The answer to this question is almost certainly "no". It is ironic that what was originally the most hyped feature of Java has now been removed. But nobody is going to miss it.

lucumo 5y ago

I worked on one this year. You need Java 8 for it and an insanely old browser. They didn't mention the applet part in the job description. That was my shortest tenure ever, including Summer jobs and internships...

msgilligan 5y ago
Ugh. Sounds horrible.
vbezhenar 5y ago
Some applets could be launched with javaws, but it would require some tinkering to extract proper jnlp file from HTML or JavaScript. I managed to do so with HP iLO remote KVM app.
- marwis 5y ago
  javaws was also removed =)
  - vbezhenar 5y ago
    Need to use old Java, yep. Not as painful as using old browser.

tablespoon 5y ago

>> Tried running a Java applet recently? ;P > The answer to this question is almost certainly "no". For me, it's a yes. My employer uses some ancient monitoring application called SiteScope. They recently "upgraded" from an ancient version to a newer one (I think the latest), and nearly the whole frontend appears to be implemented as a Java Applet. Since no browser on the Mac supports Applets anymore, their workaround was to download some Java App that ran the UI. The older version we had used HTML.

latchkey 5y ago
I love the concept that the solution is to work around the applet issue and not find some new monitoring software. I wonder how effective ancient monitoring software is.
- tablespoon 5y ago
  > I love the concept that the solution is to work around the applet issue and not find some new monitoring software. The workaround is actually part of the software itself (there are instructions right below the login box). My understanding is they're only upgrading because the old version didn't support modern versions of TLS, and there's a big push to get off of those. Finding new monitoring software would be probably be more work. At a minimum, the new version probably supports all the features we're using, and at best all our configuration can be automatically migrated. I don't know the details: I'm not part of the project, I just have an some apps with some monitors setup for them. > I wonder how effective ancient monitoring software is. It gets the job done.