What you describe is the selfish route, which isn't the cheapest. Maybe I'm naive but I still think that several developers could share the same certificate instead of paying at least 100 US dollars per year.

Java is just trying to wash money from the developers.. The apps were already really tough to launch.. I mean.. This doesn't change shit. They are trying to make it even more safe at the cost of developers freedom. What about people who put apps on the web for personal use? They can't use their app without signing it?

f**k java. "Portable"... Can't even make applets no more for personal use..

I have the same feeling than trollwarrior1, Oracle wants us to become its cash cows. If the use of a time stamp becomes mandatory, we'll have to pay both for the "trusted" certificate and for the "trusted" time stamp.

During FOSDEM 2014, Sven and Xerxes will demonstrate JiGong Web Plugin which doesn't require an authority for the authentication. Icedtea-web now supports mixed mode in applets. I still hope that Java won't die too quickly.

Java applets are dead, not much point wasting time on them, as well as pretty much all NPAPI plugin's (except probably Flash). There's no to very little need for plugins on the web these days due to the features now available with pure HTML/Javascript/CSS and probably for the better due to the security risks plugins bring. Chrome is already planning to kill NPAPI plugins, Firefox and other are probably not going to be far behind.

Hopefully someone will come up with a nice solution for easily running Java bytecode in the browser without a plugin, maybe a javascript based JVM or AOT converter to Javascript. There is stuff like GWT but it has its limitations. The current hot plugin-less tech's like ASM.js, Emscripten, WebGL already allow some really impressive stuff in the browser so a solution based on them or similar tech is IMO the way forward.

There are still use cases for applets... I recently had to create an applet that signs a message using a client certificate... that was a hurdle in itself (java 1.6 at is the target JVM... thank god!) but it was not possible using html/css/javascript otherwise I would have done that as the project is a .NET MVC application.

Java applets are dead, not much point wasting time on them, as well as pretty much all NPAPI plugin's (except probably Flash). Chrome is already planning to kill NPAPI plugins, Firefox and other are probably not going to be far behind.

There's no to very little need for plugins on the web these days due to the features now available with pure HTML/Javascript/CSS and probably for the better due to the security risks plugins bring.

HTML5 just moves some risks from the (optional) plugins into the web browser itself, it doesn't mean that HTML5 is a lot safer but the NPAPI is a real source of security flaws. I admit that HTML5 looks already cleaner than the applets but the plugins are still necessary to go beyond what HTML/Javascript/CSS are able even though they have become less useful. HTML/Javascript/CSS can't do everything. Mozilla has a weird vision of what should be the Open Web. A Web that closes the door to all plugins without distinction is not what I would call the Open Web.

Hopefully someone will come up with a nice solution for easily running Java bytecode in the browser without a plugin, maybe a javascript based JVM or AOT converter to Javascript. There is stuff like GWT but it has its limitations. The current hot plugin-less tech's like ASM.js, Emscripten, WebGL already allow some really impressive stuff in the browser so a solution based on them or similar tech is IMO the way forward.

Plugin-less technologies are "trendy" but WebGL is still far behind JOGL (and any other actively maintained Java binding for OpenGL) as I explained in details here and the same is true for HTML5 versus Java2D. Have you ever tried to play with Pirates love daisies and Runestone Defense with a Samsung S3 4G or a low end computer (AMD Sempron 2600+)? The former can't be run on the smartphone and only shows less than one frame per second on the low end computer, the latter works less badly. Breaking The Tower doesn't work on the smartphone of course but it is a lot faster than those HTML5 games on the low end computer. In my humble opinion, Java to Javascript solutions can improve the current situation in terms of deployment and ease of use for the end users but some purely Java based technical answers are still possible and that's why JiGong Web Plugin exists.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org