15 ms·

s/Apple Silicon/ARMv8 AArch64/ A lot of times it is due to direct or indirect dependencies. Before the M1 there weren't many ARMv8 AArch64 users. Only a couple

s/Apple Silicon/ARMv8 AArch64/ A lot of times it is due to direct or indirect dependencies. Before the M1 there weren't many ARMv8 AArch64 users. Only a couple of distros starting providing ARMv8 AArch recently and even then not a lot of their packages could be built for that target.

planb 5y ago
The Dropbox client exists for iOS and writings were on the wall that macs would switch to arm. This is simply a sign of wrong priorities.
- jonny_eh 5y ago
  Dropbox for iOS and Desktops are very different applications.
  - planb 5y ago
    That does not change the fact that Dropbox could have made the Mac UI easy to port as soon as it was foreseeable that apple eventually will go arm only. So they had at least 2 years.
deleted 5y ago
[deleted]
fulafel 5y ago
It's the most common Android platform, so has a lot of users overall.
- fabianhjr 5y ago
  Most Android development targets java bytecode targeting the Android Runtime which uses an OpenJDK VM/Runtime (Previously Apache Harmony) Hardly translatable to most non-java software on distros.
user-the-name 5y ago
Not the same thing. Apple uses a different calling convention, so code compiled for Linux AArch64 is not equivalent to code compiled for Apple "arm64".
- fabianhjr 5y ago
  Yeah, x86 is infamous for having a single, unique and consistent calling convention. I guess Ryzen should be called "AMD Silicon" instead and any binary not compiled with at least `-march=znver1` features should be considered "Not having native support of AMD Silicon"
- yjftsjthsd-h 5y ago
  Wait, is that a CPU difference or OS difference? I though calling convention was set by kernel, not ISA.