As I age I realize you need to entice the user with more value and service - anew features. It cannot just be quality, but quality is table stakes and the minimum expectation. When things get out of hand organizationally it makes sense to call for a snow leopard, but it comes at great cost so you better make big changes in the system so the same mistakes are not repeated.
Snow Leopard was a refinement of Leopard, and both releases had unusually long durations as the newest release of Mac OS X, totaling 4 years. It then continued getting security updates until late 2013, another 2 years after Lion replaced it. I can see how people would treat the later point releases of Snow Leopard as a high point for stability because of the years of bug fixes that had gone into the system by then.
> As I age I realize you need to entice the user with more value and service - anew features. It cannot just be quality, but quality is table stakes and the minimum expectation.
I don't know anybody who's switched to Mac because of a feature they added in the latest OS release. It's always because of the better price-performance, the better battery life, or because Windows got too glitchy and annoying. The only new Mac OS feature from the past few years that I can even name off the top of my head is when they finally added window snapping with Sequoia.
redefine what is major, scale that back and ship in a year cycle and not necessarily need to ship anything that pushes you past the threshold of "we're still beta testing even after release, and now the users are the QA team". just bring that definition of "a major software upgrade" back a bit. everyone should do it, i'd be super happy if "major upgrade" meant a new icon set and some exciting thoroughly vetted new utilities/apps. thrilled even.
Call me an old man, but I'm no longer sure that annual major OS upgrades are even desirable.
Adding features is great, but half of the changes feel like product manager brain "changes to show we made changed things".
I actually don't need buttons moved around in photos/mail/finder annually. I don't need the design language of the windows changed annually. I don't need the icons of all my apps to change annually.
An OS is a tool that serves the purpose of granting me access to all my other tools (apps).
What about the recent macOS releases that seem to prioritize dubious features (Apple Intelligence) that don't add a lot of value (and don't work well), while botching the core fundamentals of UI design and functionality, as with the UI disaster that was Liquid Glass (not to mention the broken window resize region, inconsistent spacing and corner radii, menu items being hidden under the notch, the off-center Windows menu, scrollbars that are either invisible or hard to target, etc.) Liquid Glass was inexcusable as it opposed the fundamental UI principles of clarity and legibility. Apple basically ignored its own design principles.
When companies use to charge for OS … and the releases were staggered by 3-4 years, I would have agreed.
But when OS upgrades are free, and happen yearly - there’s a different user expectation.
I'm not sure this is a good place to debate my article when the author of the submitted article merely linked to mine.
It appears that Ruben Schade downgraded to 10.5 from 10.6.2, which was still pretty early in the Snow Leopard cycle, then "tried it again a few months later" and downgraded again, until 10.7 Lion (which I personally hated and skipped on my main Mac). Thus, Schade never experienced the later versions of Snow Leopard that everyone remembers fondly.
• 10.6 was not primarily about bug fixes
• 10.7 was buggy and its design was incoherent
• Apple should abandon its yearly release cycle
That said, my recollections from the time are that the 10.6 GM release caused fewer problems than the 10.5 GM.
It wouldn't surprise me if the consensus about Snow Leopard switches to the opinion that Snow Leopard was no better than any other version. That's wrong, but few people still use or remember using Snow Leopard.
Snow Leopard was a great experience for me. So much more stable, and the OS felt tighter, like lots of the little wonky things got sorted out. It well deserves its credit and more operating systems should focus on bug fix releases once in a while.
You’ve definitely hit on the core of the issue with the Snow Leopard myth, though: comparing the final battle-hardened bug-patched version of an OS, to a newly released version. Seems like “Snow Leopard” always gets trotted out whenever someone is unhappy with the latest release.
10.9 my personal “Snow Leopard”. It has most of what made the Aqua era releases good with some QoL/polish improvements. If I could patch it with non-flat scrollbars and 10.5/10.6 2D grid spaces it’d be perfect.
You have to remember that 10.5 was a bad and slow release. 10.6 cleaned that up, and gave you a lot of storage space back alongside the fixes and improvements.
There was even an infamous data loss bug involving guest accounts (https://www.reuters.com/article/lifestyle/snow-leopard-bug-d...)! But people have forgotten about that and only remember the marketing now.
More dot releases fixed stuff and people grew used to its quirks (which there were many).
Note that the lull also lined up with the intense focus and high development pace Apple had on iOS in the early years. Ironically making the commentariat of the time ask if Apple had given up on the Mac.
https://blog.rongarret.info/2009/08/snow-leopard-is-disaster...
Consistent with this article's take on the situation 17 years later.
People forget these things after they get patched out and time passes. What's left behind as memories fade is a feel-good mythology about a bug fix release that never really existed. The truth was that engineering resources had been shifted to iOS, which delayed Leopard, and the "no new features" marketing was a way of justifying the lack of resources.
The myth part, is of course, a myth, and good marketing. Snow Leopard was super important for the OS, changing a ton: <https://en.wikipedia.org/wiki/Mac_OS_X_Snow_Leopard#New_or_c...>. Marketing gonna market.
Regardless, I can agree with this:
>People invoke its memory because they’re broadly craving stability and quality of life improvements, something almost everyone has wilfully discarded as they chase the next rung of enshittification.
I was the person who personally ran 10.6 security updates at Apple (10.6.1+), the "DRI". My team in the Updates Program office and I reviewed every single bug to determine if it should go in a security and stability update or wait for the next major version. Seriously, every morning we group triaged all Mac OS X bugs, both incoming and those nominated internally for us to look at and determine if it should go in an update. I packaged and audited the builds and tuned the delta vs full updates. I built the system that largely automated diffing "trains" for software updates (automastering).
The new version of the OS was always being developed in a branch/train, and fixes were backported to the current version as they were found. They weren't developed linearly / one after another. So, if you are comparing the most stable polished/fixed/stagnant last major version with the brand new 1.0 major version branch, the newer major is going to be buggier. That would be the case with every y.0 vs x.8. But if you are comparing major OS versions, Snow Leopard was different.
Snow Leopard's stated goal internally was reducing bugs and increasing quality. That is a fact, not marketing. I am not sure why people on the internet don't believe that, but I was there. If you wanted to ship a feature you had to get explicit approval from leadership and the bar was high. In normal feature releases it operated bottom up "here is what we are planning to ship" and in Snow Leopard it was top down "can we ship this?".
AFAIK Snow Leopard was the first release of this kind (the first release I worked on was Jaguar or Puma), and was a direct response to taking 8 software updates to stabilize 10.5 and the severity of the bugs found during that cycle and the resulting bad press. Leopard was a HUGE feature release and with it came tons of (bad) bugs.
The first .1 or .2 ALWAYS fixed critical bugs, because:
1. You had to GM / freeze the software to physically create the CDs/DVDs around a month before the release. Bugs found after this process required a repress (can't remember the phrase we used), which cost money and time and scrambled effort at the last minute and added risk. This means the bar was super high, and most "bad, but not can't use your computer bad" bugs were put in software updates...which was developed concurrently with the end of the main release (hence why .1 came out right away)
2. Testing was basically engineers, internal QA, some strategic partners like Adobe and MS, and the Apple Seed program (which was tiny). There was very little automated testing. Apple employees are not representative of the population and QA coverage is never very complete. And we sometimes held back features from seed releases when we were worried about leaks, so it wasn't even the complete OS that was being tested.
Software updates are always needed, though the issues they fix became less severe over time due to larger seeds (aka betas), recovery partitions, and better / more modern development practices. But I can tell you FOR A FACT that Snow Leopard had fewer major bugs over its lifetime, coalesced very quickly, and was extremely solid when Lion was released.
Thank you for admitting that.
> Snow Leopard was the first release of this kind
Also the last, apparently.
So maybe it wasn't peak performance or reliability that caused the feeling, but there was definitely something better about SL, and the reason I know it wasn't just nostalgic rose-tinting is because it was bookended by releases I liked worse.
Now, MS is back to ignoring users by forcing telemetry and AI. Too bad we don’t still have Steve Jobs to show them how it’s done.