It should be 'Oracle killed Java APPLETS'
It should be 'Oracle killed Java APPLETS'
No, the title's totally fine. Oracle sucks balls and killed Java. I'm still having it installed (interested in Clojure, for example), but I actively make sure that people around me Do Not Use It.
Java as a platform on the desktop was killed by the company that is
a) unable to advance the language and platform, to make it 'state of the art' again (right now, it's ... old-fashioned and limited, if you're looking at competing platforms)
b) actively trying to get malware on your machine because .. why not, you're already installing stuff from those clever people, maybe another browser toolbar would be totally fine?
[1] http://www.quora.com/Java-programming-language/Why-does-Java...
That's a pretty shitty thing, not user friendly
There's also OpenJDK as an option, though for some reason there's no official Windows builds for it.
Both Java applets and Java desktop apps are completely irrelevant to Java on the server-side.
A case could be made that Java is also an amazing success in countless devices, from Java smartcards to smartphones / tablets (with, for example, use Java source code compiled to bytecode run on something looking very much like a JVM on Android devices).
Java is an amazing success and neither Java applets nor Java desktop have anything to do with it: on the contrary, these two Java technologies hardly did anything besides giving the Java brand bad reputation.
Both Java applets and Java desktop apps could disappear overnight and the millions (!) of Java devs out there would still have a job. Granted, they'd still need one Java desktop app: the IDE they're using to develop Java apps).
Note that I'm not saying that Oracle is playing nice when, apparently, they're using spammy techniques when you install desktop Java...
All I'm saying is:
"Java applets + Java desktop apps" != Java
I have a few applications that suddenly started popping up warnings that they may stop working in a future Java release, because of a missing property in the JAR manifest (no joke, the warning actually included technical language something like this).
Certainly, though, server-side Java is hale & hearty as ever.