It’s often suggested that developing macOS on a two-year cycle, as it used to be, would result in fewer bugs or problems. What’s the evidence?
upgrade
Imagine for a moment two or three carefully chosen older Intel Macs bundled with a non-upgradable but maintained version of macOS Mojave.
Concentrate on Time Machine backups, scripts, secondary updates, and whether you still have to retain access to 32-bit software. Some hints.
In just three days last week, Apple released nine major products which demanded the attention of independent developers. How did that work out, then?
It’s got to be better than Catalina, so why not upgrade when it first comes out? Here are some suggestions to help you make your decision.
If your Mac still starts up in 10.13, now’s the time to start planning your upgrade when Apple’s support for it discontinues. Pros and cons.
How does Big Sur convince older software that it’s macOS 10.16, but to newly-built app it’s macOS 11.0?
If you have scripts or code which check which version of macOS is running, be careful with Big Sur. Is it 11.0 or 10.16?
By now, the current release of macOS has had all major bugs fixed or worked around. Isn’t this a good time to upgrade? Some practical advice on deciding and upgrading tips.
Apple is proud of high adoption rates of its OS upgrades. But 10.15 and 10.16 inevitably prevent many from using them. It’s time for Apple to understand that, and make 10.16 a macOS release we choose to use.
