I agree it is useless you spend effort on very rare case. Companies with rare compatibility needs can pay you to get such builds.
What is your direction on Linux? I remember of something like 4 of 5 different jars for various CPU that I never encountered before (I actually only use JOGL on Ubuntu + x86). Do you intend to keep all CPU compat for linux?
yes, macos-x86_64 includes aarch64 as a fat lipo universal bla blop :)
(edited, 2 times)
On Android, well, our dear client for a decade produced a commercial software (C3D)
which _also_ ran on Android besides Windows etc and was also planned for iOS (hence the port of JogAmp and producing a working OpenJDK JVM).
I'll set up a poll of Jaamsim users to try and understand why the 32-bit version gets downloaded so much, I went and checked the stats over the past year, normalized over the past few versions:
Windows 64-bit exe: 1200
fat-Jar (windows64/windows32/mac/linux): 600
Windows 32-bit exe: 200-300
Basically, the 64-bit windows exe is downloaded the most, half as many downloads of the fat-jar (which could also be windows users) and the 32-bit exe is downloaded at 1/4 or 1/6 the rate of the 64-bit windows exe. But it's been pretty stable at this level for awhile. These users could also be running a 32-bit java on their 64-bit Windows machine....will be interesting to find out what is up!
Upon further testing, noticed under Java 17 the HiDPI issues with NewtCanvasAWT are still present (apparently my laptop likes to use a pixelscale of 1.25 when I plug in the extenral monitor). Martin had collected some interesting links to different workarounds people had attempted off this tracking issue: