leftj wrote:
Here is my checklist for installing a new MACOS.
1. Install new MACOS
Works every time.
Perhaps you've never managed a help desk in IT, or managed a fleet of 45 Macs in a Windows environment? Dealing with premature Maculation is embarrassing when it loses money for your company.
The vast majority of installations ARE routine. But around 5% to 15% go awry, depending on the release, because Apple and third party developers don't think of everything before the software is released. And there are often complications we can't anticipate. It's a lot safer to wait for reviewers, early adopters, and others to find the problems.
In the photo lab where I worked, we had numerous vintages of Macs. When a new OS was released, a few of them could not handle it. So we had issues with those... do we leave them alone? Do we replace them? Do we move them to lesser roles? Replace them with PCs?
Inevitably, a new OS release would break something in Adobe Photoshop, or (way back in the 1990s) PageMaker, or FoxPro, or Binuscan PhotoPerfect flatbed scanner software. Kodak KPIS software often failed on new OS releases, so we would have to wait for Rochester to release a new version (in the next summer following an October OS upgrade). FileMaker Pro, at the time an Apple subsidiary, sometimes failed to work and required an upgrade.
I remember early 2008, when upgrading to my first Intel machine, a MacBook Pro, I had to replace all my third party software. That was a $1200 expense! It was worth it, ultimately, because the new computer was about 3.5 times faster than the PowerBook G4 and Dell Latitude 610 it replaced. But an over-budget expense never pleases the VP.
There is always a period of time between Apple's WWDC (world-wide developers' conference) and the (usual) October release of the new OS when developers are supposed to play with the Developer Preview of the next OS and tweak their software to be compatible with it and take advantage of new features. Some do, some don't. Some just need more time. Occasionally, the new OS breaks their current version, causing major headaches for users in commercial settings.
Reverting to a backup is an expensive waste of time. Oh wait, the OS upgrade bricked your machine and you don't have a backup? You're screwed! (Murphy's law of backups states that if you don't have one you will need one soon, and at the worst possible moment. But if you have one, it will be A LONG TIME before you need one.)
A little caution and patience are in order. The road to new systems is littered with the bodies of those early adopters who took the arrows of update gotchas. Anything truly new is on the "bleeding edge" of technology. I like to let the amateurs and early adopters take the hits, so that Apple and other developers get the fixes out before I need them.
The IT department where I worked was always happy to stay at least one release behind on Windows. We were still on WinXP when Windows 7 was stable. There was some inconvenience in that, but a little caution goes a long way when a $60,000,000 business is at stake.
So for me, MacOS Monterey 12.1 would be the earliest version I'd install. I didn't buy a new M1 Mac until August of 2021, about ten months since they were released. I don't like to buy from the first batch of machines off the boat. Mine came with version 11.3 of the OS, and is now on 11.6.1, which seems very stable. The new M1 Pro and M1 Max MacBook Pro-equipped Macs are out now, and getting rave reviews. I don't need one, but if I were planning an upgrade, I'd wait six to nine months, just like I did with my M1 MacBook Air purchase.
Y'all be careful out there, okay?