that's in part what makes this plan plan completely useless, and Apple got it right from the beginning back from when they announced Mac Catalyst + their decade old Rosetta tech
microsoft is such a joke, glad i am no longer dependent on windows
that's in part what makes this plan plan completely useless, and Apple got it right from the beginning back from when they announced Mac Catalyst + their decade old Rosetta tech
microsoft is such a joke, glad i am no longer dependent on windows
For one thing, a lot of code on Windows uses the .Net runtime and is JIT-compiled to the target platform. Those programs in general don't need to be ported at all.
For transitioning native x86 programs — and there are a lot of those on Windows, of course — Microsoft created a new ABI that lets you mix ARM and emulated x86 code seamlessly:
https://blogs.windows.com/windowsdeveloper/2021/06/28/announ...
This is great for something like an audio or video app that uses a lot of third party plugins. The host app can be ported to ARM, but it can still load those x86 plugin binaries. Apple has no solution for this: their Rosetta works on a process level. If you have a Final Cut Pro plugin that hasn't been ported by the developer to ARM, your only option is to run all of FCP in Rosetta emulation.
Apple has out of process plugins nowadays for that use case, through the XPC infrastructure. It's more 3rd-party SW that doesn't use XPC out of process plugins that are affected.
Given that the Surface Pro X didn't support 64 bit x86 Windows applications at all, I'm not sure how you can think so.
Even after developer channel support was added, it was unlikely to work.
>How did Microsoft screw this up? - Surface Pro X (SQ2) vs M1 Macbook Air
/Applications/1Password 7.app/Contents/MacOS/1Password 7: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64 - Mach-O 64-bit executable x86_64] [arm64]
/Applications/1Password 7.app/Contents/MacOS/1Password 7 (for architecture x86_64): Mach-O 64-bit executable x86_64
/Applications/1Password 7.app/Contents/MacOS/1Password 7 (for architecture arm64): Mach-O 64-bit executable arm64
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/
[1]: https://code.visualstudio.com/Download
[2]: https://github.com/VSCodium/vscodium/releases
[3]: https://github.com/VSCodium/vscodium/issues/597#issuecomment...
The only notable non-Universal binaries are: Calibre (Intel-only) and Podman Desktop (Apple Silicon specific build)