The following article has been updated to be more concise with respect to the way JavaFX is implemented in the various browsers. Opera does not support the Java Plugin in general.
However, I’ve been meaning to try out JavaFX for a while now, but I’ve not made the switch to it yet, simply because Opera does not support it, which is very frustrating. JavaFX has been around for at least a year now, and I’ve not found a tangible reason why it should not work in Opera. Virtually all the other browsers are capable of running it, except Safari on Windows, which gets confused and keeps asking you to install the latest version of Java even when you have it installed. I’ve searched online but all I get is the fact that Opera uses the native Java implementation instead of the plugin for running applets. So I’ve been wondering, who’s responsibility is it to get that fixed? Is it the browser makers who are supposed to implement the plugin or is it the plugin developers who are supposed to make it work in all browsers? I know Opera is written in native C/C++ and I have to ask, is the New Java Plugin written in .NET or something? What makes it incompatible with the browser? How long am I going to have to wait until I can run JavaFX applications in Opera? (Is anyone at Sun/Oracle/Opera reading this?)
I don’t like Firefox cause I perceive it to be slow (haters and fun boys, bash all your want), IE 8 is great (if you have the specs for it), Chrome is just too geeky for me (I think it lacks style) and Safari although very, very cool, just doesn’t win me over (I think it is because of its memory consumption).
Can anyone in the developer community give me some answers that might make me the next JavaFX enthusiast? Is Opera ever going to get this feature? I honestly think I have not implemented any serious JavaFX applet just because I know a lot of people would not be able to view it. For now I’m sticking with traditional applets because they are well supported and are reaping all the benefits of the JRE improvements meant for JavaFX.