I'd love to see an IntelliJ benchmark/test. As I speculated earlier, the faster IDE startup times may have a lot to do with the much faster disk read speeds.
> DO NOT use the migration assistant tool, especially not from an Intel mac. I found it frustrating to track which apps were universal and which needed updates. It also completely messed up my homedir permissions. I couldn’t even ls my Downloads folder.
Yikes, I wonder if this is a universal problem or just an anecdotal issue.
I have a lot of preferences and such built up over the years, and if I didn't use the assistant, I'm not sure how I'd thoroughly migrate everything.
I attempt to automate the setup process and my most important preferences with a couple of scripts. I keep all my dotfiles in a git repo and a script to install my most-used macOS apps and apply the hardest-to-remember system preferences. I also commit the .plist files for 3rd party apps who’s config I care about, which surprisingly is just iTerm2 and VS Code.
To prepare I do a quick pass over the script and update version numbers and such. When the new laptop arrives, I curl down my install script and run it, and I’ll end up with a Mac that works the way I expect it to with my favorite apps, but the system kind of defaults to “fresh” - I need to think about “what do I want to add” instead of “what do I need to undo or remove”.
This is more repeatable than the transfer utility, especially for employer-issued Macs. Are they gonna let me run Migration Assistant on my last day to copy state to my next employer, or my personal laptop? Nope!
I’ve used it twice this year, once last spring (from 2016 MBP to M1 Air), and then again last night (Air to M1 Pro MBP).
The spring transition was lightly rocky, had some Docker issues, a couple Node image handling packages gave me grief. I had roped off three days for troubleshooting but only needed an afternoon.
Last night’s move was flawless.
Tip: if you’ve got a Thunderbolt 3 cable, use it. No network settings necessary, just plug both computers in. My brother in law’s setup too a couple hours, mine took twenty minutes.
Does the power cable that comes with (previous generation) MBPs work for this purpose? I thought I remember seeing some talk of it being great for power but not for data.
I had no Migration Assistant specific issues migrating from an Intel Hackintosh to an M1 mac mini via a TimeMachine backup (except for the time machine backup being on a disk image on a network share, instead of the default directly on the share). I was also upgrading from High Sierra to Big Sur, so there were a TON of app permission problems. It's much worse than Vista ever was, by a mile; It's a disgrace.
Docker worked surprisingly well; it just automatically uses QEMU for all the x86 images, flagging those containers as a warning that they aren't native. I went through a hassle to get arm images to speed things up, but that just makes running builds on an x86 build agent less repeatable and images uncachable.
8 comments
[ 3.1 ms ] story [ 35.3 ms ] threadYikes, I wonder if this is a universal problem or just an anecdotal issue.
I have a lot of preferences and such built up over the years, and if I didn't use the assistant, I'm not sure how I'd thoroughly migrate everything.
There are a few ways of telling which ones of your apps are native too: https://www.macrumors.com/how-to/tell-apps-optimized-for-m1-...
To prepare I do a quick pass over the script and update version numbers and such. When the new laptop arrives, I curl down my install script and run it, and I’ll end up with a Mac that works the way I expect it to with my favorite apps, but the system kind of defaults to “fresh” - I need to think about “what do I want to add” instead of “what do I need to undo or remove”.
This is more repeatable than the transfer utility, especially for employer-issued Macs. Are they gonna let me run Migration Assistant on my last day to copy state to my next employer, or my personal laptop? Nope!
My setup script: https://github.com/justjake/Dotfiles/blob/new/mac-setup.sh
The spring transition was lightly rocky, had some Docker issues, a couple Node image handling packages gave me grief. I had roped off three days for troubleshooting but only needed an afternoon.
Last night’s move was flawless.
Tip: if you’ve got a Thunderbolt 3 cable, use it. No network settings necessary, just plug both computers in. My brother in law’s setup too a couple hours, mine took twenty minutes.
I had a true Thunderbolt 3 that I use with an eGPU handy
Docker worked surprisingly well; it just automatically uses QEMU for all the x86 images, flagging those containers as a warning that they aren't native. I went through a hassle to get arm images to speed things up, but that just makes running builds on an x86 build agent less repeatable and images uncachable.