Wasn't Java once a "write once, run everywhere"? Not that this affects me personally (I use Linux primarily; and have a Win10 machine for testing on my left hand side here), but it seems strange that Oracle supports fewer operating systems rather than more. Perhaps Oracle aims for a windows11-only Java version ... where everyone must verify his or her age.
If this is as stated, then Oracle will still offer macOS/x64 ports of Java 11 LTS, Java 17 LTS, Java 21 LTS and Java 25 LTS.
Java 25 LTS was released last year. All these LTS versions are still receiving updates. You'll only be in trouble if you need some new feature of Java that will only begin to exist in JDK 27 or later, but want to run on macOS/x64.
I guess I'm the only one who is still on x64. I don't like I'm pushed to migrate only because the software wants that, otherwise the hardware works with no problem.
> I don't like I'm pushed to migrate only because the software wants that, otherwise the hardware works with no problem.
This is one of the problems with the switch from shrink-wrap software to always-upgrading software. Customers feel like they bought a thing so it should work forever but what they are really asking is that new software be continually written for the hardware they bought years ago.
If you want to run your old hardware with your old software forever, you can. But of course in a connected world where a million malicious parties are trying to take over your system, this is probably a bad decision, and that’s where the tension arises.
If you have Apple Intel hardware, I strongly strongly strongly recommend you migrate to Linux. It works amazingly on MacOS, except I guess the sound drivers aren't perfect. Too many security holes in old, unpatched software.
Apple CEO Steve Jobs announced at May's Worldwide Developer Conference in San Jose, Calif., Mac OS X will come with a full implementation of Sun Microsystems Inc.'s Java 2, Standard Edition. It will be the only high-volume OS that does so
Oracle screwed themselves lately, the licensing push basically started IT departments with exterminating Java and anything related to it.
[Submitted title was "As of JDK 27, Oracle engineers will thus stop maintaining the macOS/x64 port", which is a quote from the article, but was a bit confusing in the title]
> WARNING: The macOS/x64 port is deprecated and may be removed in a future release.
OK, seems reasonable. Next sentence:
> There will be no guarantee that the port will build, much less function.
This... Is something quite different? This isn't what I think "deprecation" means. The message should say "no longer maintained" if that's what they mean. And it should include the "not guaranteed to build, much less function" part.
15 comments
[ 1279 ms ] story [ 2179 ms ] threadJava 25 LTS was released last year. All these LTS versions are still receiving updates. You'll only be in trouble if you need some new feature of Java that will only begin to exist in JDK 27 or later, but want to run on macOS/x64.
This is one of the problems with the switch from shrink-wrap software to always-upgrading software. Customers feel like they bought a thing so it should work forever but what they are really asking is that new software be continually written for the hardware they bought years ago.
If you want to run your old hardware with your old software forever, you can. But of course in a connected world where a million malicious parties are trying to take over your system, this is probably a bad decision, and that’s where the tension arises.
Apple CEO Steve Jobs announced at May's Worldwide Developer Conference in San Jose, Calif., Mac OS X will come with a full implementation of Sun Microsystems Inc.'s Java 2, Standard Edition. It will be the only high-volume OS that does so
Oracle screwed themselves lately, the licensing push basically started IT departments with exterminating Java and anything related to it.
[Submitted title was "As of JDK 27, Oracle engineers will thus stop maintaining the macOS/x64 port", which is a quote from the article, but was a bit confusing in the title]
OK, seems reasonable. Next sentence:
> There will be no guarantee that the port will build, much less function.
This... Is something quite different? This isn't what I think "deprecation" means. The message should say "no longer maintained" if that's what they mean. And it should include the "not guaranteed to build, much less function" part.