upvote
"Does the hardware physically work" isn't ever really the question under consideration, though, for better or worse. For Macs specifically, it is going to get increasingly difficult to even test things in the coming years. Mac x86 builds are by far the flakiest on GitHub in my experience, there's no expanding capacity, only refurbished machines 6 years out, and the number of users is dwindling, not to mention the enormous performance gap. So what do you do? When we last asked about it in a project I work on a few users expressed interest, so we kept it, but that isn't forever. The JDK as a project probably has a different risk profile than most other projects too so the cost of keeping around that code can be relatively high.

Not saying it is always good, in fact I would say there is rarely a "good" happy outcome in these cases, just trying to give the alternative perspective when you have to make these calls.

reply
> 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.

reply
The writing has been on the wall for the last 7 years and the LTS of JDK 25 goes until 2030, 11 years from the point Apple announced their intentions. Java for Mac apps or native Java backend development has always been niche as well. For Java development for Linux hosting, you still have a path forwards beyond 2030 with virtualization. How's your SPARC dev machine holding up?
reply
That's just how things go. But, existing Oracle JDK versions will continue to work, and openjdk might continue to support osx/amd64 as a target.. so I wouldn't worry too much about this.
reply
> the hardware works with no problem

In the same way that PowerPC and m68k hardware still works, sure. Apple silicon is so performant that (much like those previous two hardware jumps) it's not worth maintaining support for the old arch at this point.

reply
Java 25 is an LTS, I guess you can use that for a couple of years still. But at some point of time, macOS will be too old and all kinds of software will no longer install.
reply
Can you run Linux?
reply
Intel Macs can run practically anything. Mine had a triple-boot between macOS, Windows and Arch Linux, back when that kind of thing was possible.

Apple's really cut off gaming for good. My only hope is that someone ports FEX/Proton to macOS, or finds a way to get it running with proper hardware acceleration.

reply
Why? I can upgrade, that's not a problem. I'm just saying macOS works fine so far, almost all of the software works too. But I see increasing amount of announcements like this one suggesting that I'll have to replace hardware to get the latest versions. So I guess I will do that only to be able to use that software, not to get better performance.
reply
Well Apple isn't making amd64 systems anymore, so software support will naturally start to waver.
reply
What I wanted to say that I don't like exactly that. The hardware is fine, but software is not.
reply
I feel like Apple got a lot of devs who would otherwise be Linux users on board circa 2005 due to solid-feeling laptop hardware with drivers and power management that just worked. That pattern became self-propagating as startups scaled up, bought a lot of Macs and hired Mac IT people.

But Linux has gotten better in that time period, too. I wouldn’t say it’s quite as refined out of the box. But Linux is ahead in the ability to do whatever you want and keep using your old hardware.

For people who care about how computers work, I think Linux is a more stimulating environment than macOS to work in. Even though—or partly because—you may have to dig in a little deeper to get things working the ways you want.

reply
LLMs have completely changed how I run Linux. I just got a brand new Lenovo and getting the fingerprint sensor PAM configuration going for sudo was a breeze. I was having issues with my wifi not switching APs properly on my mesh and debugging and implementing a stable permanent fix took the same amount of time as what would previously have been just the start of me googling to the problem. And now that it's done the experience is really nice. An absolute dream even.
reply
100%, a lot of those kinds of bad linux user experience things are becoming trivial with the help of a bot.

But also the unified memory on macs is compelling for somewhat related reasons.

If it weren’t for the supply chain nightmares on top of nightmares, we’d be experiencing a nice little moment.

reply
You can install Linux on the hardware and get full x86_64 support again.
reply
Have just read above that it's possible. It's interesting actually. So I guess I'll do that once I buy a new mac. I have a maxed out pro, with i9 and so on, so throwing it await would be a shame
reply
> I'll have to replace hardware to get the latest versions

Or switch software. Windows will run via Boot Camp and depending on your hardware Linux might work too.

reply
Including Windows 11 on T2 Macs, even though there are places online that claim it doesn’t work. It’s much easier to set up Linux, though.
reply
My mid 2012 air had trouble with os x about 10 years ago. I moved to nixos and haven't had any issues since.
reply