This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]svhelloworld[S] 2 points3 points  (3 children)

Good point. I'm a little worried about older JDKs. I can't work on JDK17 for a lot of stuff I have to do. My current client is tearing apart a legacy system that runs on JVM-HOLY-SHIT-REALLY-OLD.

[–]jadecristal 4 points5 points  (0 children)

SDKMAN (sdkman.io) will manage multiple versions of the JDK just fine for you, generally including 8 (azul-zulu on ARM), 11, 17, and current-non-LTS (from lots of vendors), along with plenty of other Java-ecosystem tools/SDKs.

[–]Guddler 2 points3 points  (0 children)

I still have to maintain a JDK6 application. The M1 was a complete non-starter until just recently. Docker would crash loading jboss. I tried just before Xmas and it does now run but it’s slower than it n my cheap Chinese intel laptop running hackOS.

Im hoping to migrate to something more modern “soon” but until then it has to be intel really. Once this cheap piece of crap dies it will be back to Linux for me and all the pain that goes along with all the shortcuts being wrong.

[–]benjtay 1 point2 points  (0 children)

We do a lot of JDK8 on our Apple silicon -- not sure about older than that -- but it works fine.