4 ms·

And doesn't have any way to download it or anything. Java in browsers is officially a bad choice, people, as Chrome refuses to work with it.

• edejong 10y ago
  Technically, Chrome refuses to work with NPAPI, which Java depends on. Unfortunately, Oracle did not deliver any alternative to run Java in some of the more secured browser-plugin architectures.
  • Vendan 10y ago
    Well, Oracle has also deprecated java in the browser, so...
• mindcrime 10y ago
  You could just as easily argue that "Chrome as a browser is a bad choice" for that reason.
  • Vendan 10y ago
    or that NPAPI is really old, and that oracle is discontinuing their browser java plugin. Do you really think you can argue that Chrome is a bad choice cause it doesn't support something that is deprecated?
    • mindcrime 10y ago
      The thing about NPAPI is that it was at least a somewhat universally supported standard... and after dropping NPAPI, all Chrome offers is NaCL and PNaCL, which - AFAIK - nobody else supports. So you could argue that Chrome took a step backwards by dropping NPAPI before waiting to see if NaCL/PNaCL (or something else) would become the industry standard replacment for NPAPI. I am, of course, just "playing devil's advocate" here a bit. NPAPI clearly had issues and I'm not enough of an expert to say if it would have been possible to simply improve it, or whether it was truly necessary to go to a whole new model. And you can certainly argue that the other browser vendors could adopt NaCL / PNaCL. I guess they have their reasons for not doing so. It's sad really, because "Java on the Web" has a ton of value, but Sun screwed the pooch years ago with some of their decision making, leaving us where we are now. Oh well, at least there is JWS / JNLP. Hmm... come to think of it, I wonder if the OP could just rework their app to run as a JWS app, instead of as an applet? That might make everybody happy...
      • sideshowb 10y ago
        Is JWS/JNLP more secure? How so?