5 ms·
To be fair, no one should be using Java applets in this day and age, and hopefully this will finally kill them off for good.
by FreakyT 11y ago
To be fair, no one should be using Java applets in this day and age, and hopefully this will finally kill them off for good.
- drdeca 11y agoThough, now you can't make certain types of sockets in browser...
- mmebane 11y agoNor can you integrate with the local filesystem, or call native APIs. With a hidden Java applet, it was pretty easy to make a full-fledged application that just happened to have a web-based API. That's getting a lot harder. Chrome extensions have an API called Native Messaging which is roughly the postMessage API over stdin/stdout. It works, but isn't cross-browser. Alternatively, you can start up a local server and make XHR or WebSocket calls to localhost. However, both of those require the user going through an external install process. Maybe, in the current security landscape, that's the way it has to be, but it's kind of annoying.
- mindcrime 11y agoNot sure I agree with that. I like, for example, the Java applet that goes with FreeMind for viewing mindmaps.
- yellowapple 11y agoJava is still required for a lot of educational gizmos online (like physics demos/examples). Hopefully there'll be an effective way to keep such things alive "in this day and age".