At my church for some of our production needs we had an old i5 MacMini I had donated that was from 2011. It won’t upgrade to Big Sur so we just purchased an M1 Mac Mini. It seems to work great. Have not seen any compatibility issues. We run the Xojo written app I sell there and it works great under Rosetta. Now to start compiling for Apple Silicon…
Yes, I get Retina display.
As expected, VMWare Fusion is defeated by M1.
However, CrossOver performs quite fine.
Parallels is all set for Apple Silicon
Not quite. They did show a prototype, but their current Parallels Desktop 16 does not support AS.
Parallels Technical Preview is working fine with the latest update. I’ve been using it with the Windows 10 ARM Insider Build since I got my M1. I talked about it quite a bit here:
Is that Technical Preview available only to existing customers ?
No, you can get it and a key to use it for free while it’s in testing phase by filling out a form. I think the link was posted in the thread I provided above, but just in case it wasn’t:
And for the Windows 10 ARM Insider Build:
Thank you Anthony
OK. This parallels does not support previous Intel VM, which makes them unusable.
I regret Power PC’s Virtual PC
At least for some purposes. If you only need to run Win10, then this preview with the Insider ARM64 may go a long way.
OTOH, if you need to run prior macOS versions in a VM or older Windows versions that are Intel based (or Intel based Linux) then the preview does not help.
Windows 10 ARM Insider Build runs both 32- and 64-bit Windows Intel applications as well. If you need Windows on your ARM Mac, this is the way to go. If you need to test other versions of Windows, you’ll still need an Intel machine, but you shouldn’t be releasing software for Operating Systems you’re not testing for anyway.
I was amazed to see Chrome run under Windows ARM.
I do agree, though, that developing Windows apps without testing on an actual PC is not advisable.
There are problems trying to do this from a M1 Mac at the moment. It’s unconfirmed if this is just a ver 1.0 issue, or if that is no longer an option with arm Macs.
The great advantage with Intel Macs was that the processor was the same architecture as on Windows machines. So it really wasn’t that hard to have a great Windows virtual machine as no CPU emulation was really needed as direct calls could be made to the same CPU that is used on an actual Windows machine (overly simplified I know but still it makes a point). Now, it’s a different architecture altogether and unless you are running Windows for ARM, you would have to emulate the Intel architecture. So it becomes a much more challenging situation and possibly slower…
You could also natively run Windows on your Mac using Bootcamp. All that is now gone…
im doing this tomrrow, well, Monday
When Apple used PowerPC, IBM had a series of PC using the same processor to run Intel apps.
It should be relatively easy to leverage the same kind of technology to provide Intel emulation.
That said, I seldom use Windows on Mac, since I have a real PC in my office. I also believe nothing quite replaces developing at least the last mile on a true PC.
Up until 2017, one could develop on Mac and compile for Windows with a relatively consistent UI. Today, Xojo Windows does not provide transparency, but pseudo transparency, meaning labels, canvas, container controls take the color of the parent. Any app relying on transparent control may be unusable once blindly built for Windows.
Ah yes, but at that time Windows NT had a PowerPC version. Once Microsoft dropped PPC versions from Windows, IBM quickly dropped support of its own chip.
The PPC was actually a great architecture and it’s sad that IBM and Motorola decided to abandon it. But it’s hard to have a processor that doesn’t have support from a major OS. Funny how Apple went to the RISC architecture with PPC, then went back to CISC with the X86 family. Now we are back to RISC CPUs…
As for developing on Windows on a Mac - You think you can compile blindly. I tried it. Doesn’t work - not for Window and not for Linux either. Using a VM is pretty dang close though. It gets you 99% of the way there maybe even closer than that to 100%. There is nothing like running on actual hardware though.
The major difference is that on a Mac you get double buffered display, which effectively hides all flickering, which is the major plague of the WinTel platform.
So an app may look pretty nice on Mac, and poor on a true PC. In my experience, nothing replaces doing at the minimum the last mile on a real PC.
I even had an app (Watermark) which looks and performs quite nicely on Mac.
Once compiled for PC it became darn unusable: flicker, and even some controls did not show.
I had to completely refactor the app for it to work on Windows.
A few comments here that might be generally helpful. (I’ve just spent the past few days carefully going through and setting up an M1 MacBook Pro 13" 16GB/1TB to use in addition to an older 2017 15" MBP. (Still going to need the 2017 for Windows VMs and certain other things that won’t run on the M1… but the goal being, to move as much active development for various projects onto the M1, and to retain the 2017 as a working backup).
“Why”? The 13" M1 is much faster and better than the 2017 15" (which cost twice as much as this did) in every way. (Other than: can’t run Windows Intel VMs; 2 ports instead of 4 (can be worked around with a dock); only 1 external display (annoying); and can’t run any older 32-bit applications). Perfectly silent. Instant. Also twice as much space (the 2017 only has 512GB instead of 1TB, and did I say that it cost twice as much as the M1? )
For anyone getting a new M1 system, some recommendations:
- Before doing anything else, start it up and update to Big Sur 11.1 from the 11.0.1 it shipped with. Create a new user account matching the long username and home folder short name of the system you’re going to migrate things from. Then after you’re up and running fully with 11.1, use Migration Assistant to copy over everything from the user account of your previous system (whether you’re going to continue to use that, as I am, or not). This is a little non-obvious if you haven’t done it before.
- Have both Macs on the same WiFi network (but they’ll connect peer-to-peer for the actual transfer, and higher speed than going indirectly through your router). Run Utilities:Migration Assistant on the M1, tell it you’re going to copy from another Mac. Then it starts searching for sources. Run Utilities:Migration Assistant on the “source” Mac and then it’ll show up in Migration Assistant on the M1. Pick and choose what you want to copy (can be multiple user accounts) and let it go. In the end, you’ll have everything you need as a starting point on the M1, including the contents of your keychain, signing certificates, etc.
- Log into the M1 when its done, Most/nearly everything you have in the source Mac will now be hooked into on the M1 - Mail accounts, logins, etc. You’ll have to sign back into iCloud, the App Store, etc. and jump through a few hopes. Get everything running, piece by piece. (This approach is much faster and easier than starting “plain vanilla” and reinstalling every single thing manually.
- Go through things in the Applications folder, update App Store things, etc. Parallels will copy over but your Intel VMs won’t work, so unless you’re going to try the M1 preview, leave it alone. You can use the extremely useful Archichect application from https://eclecticlight.co to drag-and-drop applications onto it and check to see if they contain Apple Silicon code or are just Intel. (it’ll also check code signatures at the same time).
- Get Xojo and all of your development tools up and running. Use 2020r2.1 and the latest Universal plugins from various sources. Should be able to build and debug either Intel under emulation or Apple Silicon natively, depending on how you set the build target. (that’s where I am now).
The M1 laptop is hugely fast, perfectly quiet, barely gets warm, and it’s by far the best Mac I’ve used in 35+ years of development.The small “early” hardware limitations (2 ports and only 1 external display) are a tiny disadvantage compared to the benefits.