The main selling points of Java is that it can actually be used on any computer. All that the computer needs is an interpreter for Java bytecode. Such an interpreter simulates the Java virtual machine in the same way that Virtual PC simulates a PC computer. Theoretically if you write a Java program well, it should work on any computer, and for many years to come.
In practice there have been too many times where a certain Java program cannot be used on the computer you want to use it, even the computer has Java support in it. I have seen too many cases where a device configuration tool or user interface written with Java has become unuseable very soon, and you just can’t use that on modern computers. A typical case is that Java application has run nicely on some old Java version, but refuses to run on some newer Java version. And when you have a newer PC, you can’t get the needed very old Java version to that PC in any practical way. And the manyfacturer does not provide any updated softwere. So the somewhat old still well working hardware or software system too soon becomes unuseable, because the Java based user interface just don’t work.
Java is supposed to run on any PC, but in practice many Java application just don’t work. Why does many Windows program seem take better time (even very old version runs nicely on modern Windows version or Windows emulator on Linux system)? Is the problem that Java keeps changing too much too often (problem to compatibility) or are the Java applications just so baddly written (in incompatible way)?
Thats really the Truth.
But i dont have Problems under Linux with Java, only in Windows.
Thanks
Frank
Thank You For This Post, was added to my bookmarks.
very good post
Canonical To Remove Sun Java From Repositories, Users’ Machines
http://developers.slashdot.org/story/11/12/18/1425230/canonical-to-remove-sun-java-from-repositories-users-machines
“Apparently, Oracle’s ‘Operating System Distributor License for Java’ is expired, causing Ubuntu to not only remove sun-java from the partner repository, but from user’s machines.”
http://www.omgubuntu.co.uk/2011/12/java-to-be-removed-from-ubuntu-uninstalled-from-user-machines/
From the article: “Oracle, in retiring the ‘Operating System Distributor License for Java’, means Canonical no longer have permission to distribute the package.” So it’s not that Oracle has lost their right to distribute Java (JDK) or something, but they are retiring the license Canonical is using that granted them the right to distribute it with Ubuntu. The summary also states (correctly) that Ubuntu will remove the sun-java package from the repository and user’s machines, but does not state why: “Due to the severity of the security risk, Canonical is immediately releasing a security update for the Sun JDK browser plugin which will disable the plugin on all machines.” Ubuntu’s Marc Deslauriers wrote in a mail to the Ubuntu Security Mailing list.
Comment:
It’s being replace by OpenJDK. It was planned to happen like this for years. This was planned obsolescence with a gradual move to OpenJDK. Their is no surprise here except for those who didn’t know it was coming. The summary is inflammatory but if you read the article you see that this is nothing really.
OpenJDK is still the default, and still distributed. And like TFA pointed out, the Sun/Oracle version is old and has security issues anyway.
Java Considered Harmful
http://www.f-secure.com/weblog/archives/00002285.html
Do you need Java in your web browser? Seriously, do you? If not, get rid of it.
Turns out, most users don’t need Java any more, yet people keep running it.
The risks of Java are nicely illustrated by the recent Java Rhino vulnerability (aka CVE-2011-3544). If you’re running Java, but not the latest version, you’re vulnerable. So either you have to check at all times that you have the latest version of Java — or get rid of it altogether.
And the Java Rhino vulnerability is not theoretical: the most common exploit kits have incorporated this vulnerability in their default exploits, and it seems to be working very well for the online criminals.
So, ditch Java if you can. It might not be as painful as you think
Also note that Chrome has been doing a good job in sandboxing or otherwise securing risky add-ons and extensions. Many Java exploits do not work against Chrome. Also, Chrome does not use an Adobe Reader plugin to render PDF files.
Java roadmap: Oracle’s two-year plan
The company is planning aggressive moves for the critical software platform in the next few years. Here’s a rundown
http://www.infoworld.com/slideshow/28552/java-roadmap-oracles-two-year-plan-185238