3 ms·
I'm really worried - there's software that I rely on such as parts of the JVM ecosystem that haven't had as much much work put into them for ARM as they have fo
by chrisseaton 6y ago
I'm really worried - there's software that I rely on such as parts of the JVM ecosystem that haven't had as much much work put into them for ARM as they have for Intel. How long do we have to bring things up to speed? Just a year? Obviously everyone has known this is coming but I haven't seen much action yet.
If we get the worst case scenario and Apple ships only ARM hardware from January 2021, then I feel like there's going to be some serious problems.
- tonyedgecombe 6y agoIf we get the worst case scenario and Apple ships only ARM hardware from January 2021, then I feel like there's going to be some serious problems. That seems extremely unlikely to me.
- paulio 6y agoyes, I can't imagine docker is going to be happy either.
- p0rkbelly 6y agoIt seems that the initial plan is that only "MacBooks" aka budget macs will have the ARM cpus. The Pros will remain x86....for who knows how long though.
- rjsw 6y agoFrom the OpenJDK commit logs aarch64 seems to have been getting a fair bit of attention over the last year. I do run OpenJDK on aarch64 and it seems fine but I don't run anything particularly serious. If Apple ship an AArch64 machine with plenty of RAM then it would make a big difference to what applications people try to use.
- dehrmann 6y agoI think the complaint was more about libraries using JNI than the JDK, itself. There's a popular sqlite library that ships with native libraries, otherwise falling back to transpiled code. I'm not sure if they've done much work for ARM. Java's actually the easy case. ARM means a lot of docker containers won't work, your development architecture is different than your protection architecture, cython libraries, etc. This is probably the right move if you want to build a laptop with good battery life, but sort of like removing the escape key, it's problematic for a large segment of Mac buyers.
- chrisseaton 6y ago> I think the complaint was more about libraries using JNI than the JDK, itself. No it's the compilers in the JDK, at least in my case.
- chrisseaton 6y agoFor me it's the new compiler - Graal - many people say it isn't as tuned for AArch64 and some people have claimed its architecture isn't brilliant in all places for AArch64 either which could be a longer-term problem. I push the Java compiler pretty hard so a few % regression over C2 on AArch64 would be pretty nasty for me.
- michelb 6y agoI'm pretty sure the first device will be a low-end laptop. It should be great for that as the iPad shows. I'm really not convinced they have anything that can rival the iMac/Intel for extensive load.
- floatingatoll 6y agoIIRC, and it's been 15 years, for the last transition they sold prototype towers that could only be purchased and operated by folks with an active and current Apple Developer account, and did not make consumer hardware available for 15 months after the June announcement. So at the first WWDC the developers get a one year head start to work with Apple to get everything ready for the new platform, and then at the second WWDC Apple finalizes the launch plans and sets the launch dates for new hardware. It seems likely that Intel editions of the 16" MacBook Pro and the Mac Pro will continue to be sold after September 2021, due to hardware DRM dongle issues — and it's likely that they'll keep around an Intel Mac Mini as well. Given that ARM is now a datacenter option, it's probably time for the JVM ecosystem to stop being Intel-only in any case, but historical evidence suggests you have at least 15 months before general developers have any hope of buying one of these.