4 ms·
I think the breakdown is with native/non-native apps and specific build systems. Pretty much all the native apps that get updated for M1 are universal binaries
by cwizou 4y ago
I think the breakdown is with native/non-native apps and specific build systems.
Pretty much all the native apps that get updated for M1 are universal binaries. Xcode is (all things being relative) pretty good at making this work semi-transparently.
The only instances where I see separate builds for x86/M1 is with non native apps, a good example that I saw just yesterday being Postman. I would guess either their build system is the culprit, or some libraries that they rely on. It's not systematic though so this is particular to those vendors, it could also be that they chose to do separate builds for other reasons, though it's not what Apple suggests developers do.
Teams and Discord both have universal builds and are non-native, as counter examples to Postman. Another good example is that while VS Code [1] is universal, VS Codium [2] makes separate builds (those seem to have been posted in the last 12 hours, yay !), and this is mostly due to their build system [3].
This site is also a good resource that tells you what has native M1 support, and what still runs under Rosetta : https://isapplesiliconready.com/ https://isapplesiliconready.com/
[1]: https://code.visualstudio.com/Download https://code.visualstudio.com/Download
[2]: https://github.com/VSCodium/vscodium/releases https://github.com/VSCodium/vscodium/releases
[3]: https://github.com/VSCodium/vscodium/issues/597#issuecomment-1112877775 https://github.com/VSCodium/vscodium/issues/597#issuecomment...