3 ms·

JavaOS was DOA and end-of-lifed in 1999. Superseded by J2ME, which didn't support applets, as least not without an application-specific loader, or within a web

JavaOS was DOA and end-of-lifed in 1999. Superseded by J2ME, which didn't support applets, as least not without an application-specific loader, or within a web browser AFAIK. I'm pretty sure it's safe to say that Java applets on bare metal never took off. As has been pointed out in another response, "running Java applets without an OS or browser" was not exactly the intent of the OP's words in any instance.

pjmlp 8y ago
You are missing the embedded and factory automation market, blu ray players, cable TV boxes, where plenty of JVM vendors are happily selling bare metal JVMs. The ones that never had any issue with either Sun or Oracle, because they always played by the license rules.
- nineteen999 8y ago
  I'm not missing anything. You can keep moving the goal posts all you want. The conversation was about applets, running in a web browser, and how a browser AND the the JVM's available at Java's release, did or didn't require an operating system to run. Embedded Java is not "applets". Nobody is denying that there is billions of devices running client side Java code. https://www.v3.co.uk/v3-uk/news/2443810/oracle-signals-the-end-of-java-applet-support-for-browsers https://www.v3.co.uk/v3-uk/news/2443810/oracle-signals-the-e...
  - pjmlp 8y ago
    > The web browser/JVM certainly needed an operating system to run, and by extension the applets did too. Not moving goal post at all "JVM certainly needed an operating system to run".
    - nineteen999 8y ago
      It certainly did at the time that Java was released, which was the context I was commenting in (ie. "needed", not "needs") - the original HotJava browser (1994) or Netscape 2.x (1995) with builtin Java applet support, before it was later moved to a plugin. JavaOS wasn't released until later (1996). And Wikipedia classifies it as an "operating system with a Java virtual machine as a fundamental component". The clue is in the name.

pjmlp 8y ago

You are missing the embedded and factory automation market, blu ray players, cable TV boxes, where plenty of JVM vendors are happily selling bare metal JVMs. The ones that never had any issue with either Sun or Oracle, because they always played by the license rules.

nineteen999 8y ago
I'm not missing anything. You can keep moving the goal posts all you want. The conversation was about applets, running in a web browser, and how a browser AND the the JVM's available at Java's release, did or didn't require an operating system to run. Embedded Java is not "applets". Nobody is denying that there is billions of devices running client side Java code. https://www.v3.co.uk/v3-uk/news/2443810/oracle-signals-the-end-of-java-applet-support-for-browsers https://www.v3.co.uk/v3-uk/news/2443810/oracle-signals-the-e...
- pjmlp 8y ago
  > The web browser/JVM certainly needed an operating system to run, and by extension the applets did too. Not moving goal post at all "JVM certainly needed an operating system to run".
  - nineteen999 8y ago
    It certainly did at the time that Java was released, which was the context I was commenting in (ie. "needed", not "needs") - the original HotJava browser (1994) or Netscape 2.x (1995) with builtin Java applet support, before it was later moved to a plugin. JavaOS wasn't released until later (1996). And Wikipedia classifies it as an "operating system with a Java virtual machine as a fundamental component". The clue is in the name.