Slashdot Mirror
Java 6 EOL'd By Oracle
Tmack writes "Not completely unexpected, Java6 has reached EOL. This tidbit shows up in Oracle's Java6 FAQ page, recommending everyone update to Java7: 'Oracle no longer posts updates of Java SE 6 to its public download sites. All Java 6 releases up to and including 6u45 have been moved to the Java Archive on the Oracle Technology Network, where they will remain available but not receive further updates. Oracle recommends that users migrate to Java 7 in order to continue receiving public updates and security enhancements.' Apple just pushed its update 16 which is Java6u51, likely to be one of their last Java6 updates."
Hating Oracle just feels right. All the pointless rage we deliver to Microsoft for terrible, greedy business decisions, plus they kill popular open source projects. It's like being young and in love, except the opposite of that.
I know why they don't, but I wish they would auto update everyone on 6 to 7. Bugger.
I don't like Java 7, it feels dirty. I will keep on with 6 for now
(That was sarcasm, BTW. It pays my bills too -- and quite nicely. I expect its benefits as a technology to be completely wasted on the 14yos that infest these boards though.)
Do you have any Idea how old Java 6 is? It's not a question of keeping two version active at once. It's about it's age more than anything. Java 6 was released in 2006. It's not like their EOLing it after 2 year. Support has to end some time, and 7 years is longer than I would have kept it.
I still have sometimes to use tools that were developed for Java 1.3.1 and barely run with Java 1.4.2.
I wish Oracle were end of lifed.
but when you have to issue 10 updates in 6 months, that's pretty bad.
Poppycock.
I can't remember ever having my Ubuntu LTS servers go a week without security patches appearing, usually the same few bits of software; the kernel, glibc, apache, mysql, etc. Java SE models an entire machine, provides a vast application API and a powerful optimizing compiler on multiple platforms. It's a mighty piece of software and flaws abound. The real problem with Oracle and Java has been the lack of updates. By rights Java 7 SE should be on about update 110 by now. One a week.
Maw! Fire up the karma burner!
Do you have any Idea how old Java 6 is?
Do you have any idea how new Java 7 is? It's just about two years old, but that makes it sound older than in reality, because for the first year it was out Sunacle were very clear that it was still "beta quality" and that developers should stick with Java 6. It wasn't until about a year ago that Java 7 really "rolled out" as the replacement for Java 6.
I can't remember when IT first allowed Java 7 onto our desktops, but I think it was less than a year ago. Even then, it's still not the "official" version of Java because there's some IT-related software that can't run on Java 7. Not to mention that some of the software I work with also can't run on Java 7 due to JNI incompatibilities. (Man I wish we could ditch that, but I didn't write the component that uses that component, so...)
In any case, no matter how old it is, Java 7 still isn't quite ready to replace Java 6. Especially under Mac OS X, thanks to the transition between Apple and Oracle supporting Java. Although I don't know who's really to blame for that one, Apple or Oracle, but they can both take the blame as far as I care.
The point is that I still use Java 6 on a day-to-day basis, and it's not from lack of trying to move to Java 7.
You are in a maze of twisty little relative jumps, all alike.
what bugs me is that they keep trying to get me to install the Ask toolbar every time I update Java 7.
Perl
Do you have any Idea how old Java 6 is?
Doesn't matter. There are a *lot* of applications that not only require Java 6, but a specific point release of Java 6.
"Write once, run anywhere" my ass.
They should let Kronos know that it's unacceptable that they don't update their software to be compatible with the latest JVMs. If enough people bitch, they'll fix it.
Are agnostics skeptical of unicorns too?
By "a *lot* of applications" you mean things like SAP or other Enterprise traps ?
It takes a bit of work to write Java applications that are version-dependent, it's hardly ever an 'accident'.
After at least 3 years of perpetually the worst thing to happen to browser security ever, maybe they should just eliminate their entire web plugin. I mean for God's sake, I just saw someone's credit union use a java app for logging into online banking. I've never heard of a bank demanding that its users purposely ruin the security on their computer in order to access online banking. I heard v7r25 that was released days ago already has critical flaws. I think technically if you had Java for the last 3 years, there wasn't one moment in time that you were actually without a gigantic java-based exploit security flaw.
People who don't think java7 is ready are smoking crack. It's been production ready for a long time.. Works on Linux, works on OSX, works on Windows. I have used it on 20M transaction/day apps and had it run for months with no issues.. Java gets a bad name because of the browser plugin. Let's EOL that for all versions of java. I like java on the server. I like it for writing Android apps. I do NOT like it in the browser, and neither does anyone else with any interest in security.
- Vincit qui patitur.
People don't tolerate neglect; they just go find alternatives.
some even might go find alternatives to java altogether ... oh wait. not really, because most people tends not to look for alternatives at all, and actually tolerates shitloads of bullshit. that's why companies like oracle exist.
Java 6 will still run.
Actually, no, sometimes it won't. I have personally spent most of today fielding support problems because the "improvements" in Java applet security in 6u51 (mainly for Apple users) and 7u25 have meant precisely that systems that were working just fine yesterday are not working today.
It's like people think "Set build option X and it'll work again" or "You need to sign it with magical certification Y at time Z now" is a viable response. In reality, many Java applets are used other than as part of a maintained public web site, and once deployed maybe they can't easily be updated. They might be part of a secure intranet where any changes need expensive regulatory approvals to be redone. They might be part of a user interface embedded in network-accessible hardware. It might just be a useful demonstration on an academic's web site that they wrote ten years ago but don't maintain. In the last 48 hours, these and many other cases all broke.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
And every time Larry thinks about cutting people like you off from any support or updates whatsoever, he gets a warm feeling where his heart would be if he had one.
Java moto: Write once, fuck you.
http://superuser.com/questions/549028/how-can-i-prevent-ask-com-toolbar-from-being-installed-every-time-java-is-update/562869#562869