I don’t necessarily agree with Jeff Johnson’s conclusion that major software upgrades are impossible on an annual schedule. I also don’t know what he’s looking for, as someone who worked at Apple during this time quality improved substantially in 10.6 Snow Leopard and continued. Most bug fixes don’t get a marketing line item or even much fanfare. We were all users of what the OSX guys were doing and lived on the dogfood while we made our own mistakes on iOS.
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.
> As I age I realize you need to entice the user with more value and service - anew features
Is this true of operating systems for most people?
Personally I’d take macOS from 15 years ago (with security bug fixes and new hardware support, assuming modern apps still worked, but no new features) over today’s Windows any day.
No one said major software updates are impossible on a yearly schedule. It's obviously possible since Apple's been doing it. What's not possible is major software updates with a normal amount of new features for a major software update at a reasonable level of quality
YMMV. I ran Snow Leopard on a couple of machines for years—bought it off CraigsList for $10, handed off in Times Square—and it was far and away the best OSX experience I had, and, at least in my experience, the best/smoothest/most stable until El Capitan, 10.11. And yes, maybe I'm thinking of 10.6.8, but I don't see why that's a problem.
>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.
As I recall, there were plenty of legitimate user gripes when the very first iteration of Snow Leopard (10.6.0) was released. But by the time of the very last point-release (10.6.11?), the OS was rock-solid. It was only after all the initial bugs were ironed out, that Snow Leopard achieved the legendary status that it has enjoyed ever since. The blogger doesn’t take this factor into account.
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.
fond fond fond memories of Snow Leopard. I was just a kid back then, so I guess I missed the complaints that people are mentioning here, but even back then no shiny new features but an improved and refined product seemed like a good/brave idea. something I'd like to see more of.
Wasn't a lot of Snow Leopard an exercise in removing old cruft from the PowerPC architecture, and the last release to support 32-bit Intel machines? From my perspective at the time, it was really meant to set up Mac for the next decade or so, which it did brilliantly.
Another underlying reason snow leopard is so fondly remembered is it was the final purely Mac version of Mac OS X. Starting with lion the focus shifted to bringing iOS-like features and design to Mac OS X. And it has never been Mac first since.
The final SL point release was very stable. Still is. Lion was a horrible and nasty release which shouldn't have seen the light of day. FWIW, SL introduced several new UI elements into OS X as they needed something to show off at release. Something. Anything.
I don't agree, as someone who lived that era. Snow Leopard was the best OS X release in terms of performance, made immediately apparent by the disastrous release of 10.7 Lion and several years beyond.
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.
I remember going from Tiger to Leopard and thinking "this is nice, I like a lot of these changes" and then going from Leopard to Snow Leopard and thinking "wow this is great". Then Lion came along and I was like "this is meh".
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.
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.
Windows Vista came out and everyone hated it. Microsoft ignored everyone and said, “You fool users just don’t understand what makes a good operating system.” Snow Leopard was the next major OS release and it just worked the way people expected an OS to work. Paired with solid understated marketing, it felt like users were respected for their choices in an OS once again. MS was forced to follow suit with W7.
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.
People had difficultly opening the plastic case it came in. I did. Ms added a red pull tab to indicate an affordance, then later changed the case to a simple clam shell for Windows 7.
I'm sorry, but this is horseshit. Snow Leopard is beloved by the Mac user base for a reason. It was legitimately faster and more stable than any prior release.
Oh, this again. I should put a website with this up...
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.
It was definitely a great release. I think that’s a big part of why it’s become legendary.
To me the myth is the “no new features”. Apple may have said that in places in marketing but there were new features. Grand Central Dispatch for example.
Yeah as someone else that worked on Snow Leopard I found this article and ones like it a bit silly. They're a lot like the old "debug code" posts on Mac forums back in the day trying to explain why Puma was slow (no, you've got a G3 and an unaccelerated video card).
Tiger and Leopard were sprawling releases. Tiger covered 32-bit and 64-bit PowerPC, then 32-bit x86, then 64-bit x86 Macs. Tiger was also what I guess I'd say is the first "modern" OSX release, with subsystems like launchd and a more mature OpenDirectory replacing older NeXT subsystems.
Leopard in my experience was a train wreck. It shipped a lot of new features, both user facing and back end frameworks, but the development was seriously impacted from teams losing engineers to iOS. Leopard had features planned assuming 100% availability of SWE's resources but ended up with 40-50% of SWE's resources (made up numbers based on my feels at the time). Many new frameworks in Leopard did not land or get stable until very late in the development cycle which meant everything downstream had to scramble right before GM. It was 100% the case that Leopard was not really stable until 10.5.8 and still sucked IMHO.
There was a lot of clean-up needed in MacOS and that was Snow Leopard. It was not a perfect release but 10.6.3 (the second disc pressing IIRC) and onward were very stable. Dropping PowerPC support really helped focus QA since they didn't need the massive array of test hardware Tiger and Leopard required. You also didn't need to wrangle builds for four architectures, including multiple compilers as a few libraries (if not whole frameworks) were compiled with ICC on x86 for performance reasons.
The "Snow Leopard wasn't that great" meme is weird. I'm sure it had its problems like every OSX release did. Unfortunately most OSX releases broke someone's workflow[0]. Snow Leopard ware no different. But it was always billed internally as a "no new features" release and those features that it did ship faced a very high bar to get in the release. I definitely look back on Snow Leopard as a high water mark for macOS quality in terms of a release.
From the outside, Tiger always seemed insanely multifaceted. Supported the four architectures you mentioned AND was the only release to have both Rosetta and Classic mode. Despite all that, it seemed pretty stable.
There was something else going on during that time period though.
Consumer operating systems in the 1990s were pretty bad. Windows 9x and MacOS Classic didn't even have protected memory. They crashed a lot.
Microsoft fixed this with Windows NT (delivered to consumers as Windows XP), Apple with BSD/NeXT (delivered as OS X). It was the point when ordinary people first got computer operating systems that were fully baked. But the earliest versions (Windows NT/2000 or NeXTSTEP/OS X pre-Snow Leopard) still had the problems that come with new code, so the later releases were better. Hence, the best version of MacOS was Snow Leopard and the best version of Windows was XP (or, depending on who you ask, 7). Because that's when they finally made a decent release.
Once we had operating systems that do essentially what operating systems are supposed to do, since then it has felt like nothing but lateral moves and deterioration because there wasn't much left on the table for newer versions to win but every update is another chance to break or lose something we used to have.
It's rewriting history to say that OS X didn't have a decent release before Snow Leopard. Panther and Tiger were both excellent releases and Panther was widely considered the first truly usable OS X release. That's when it got decent.
I was there too, but this blog post agrees with my memory.
I agree with you that Snow Leopard was billed as no USER VISIBLE features. But people did NOT just fix niggling bugs, it was an architecturally huge release. E.g., it introduced GCD. And unless I’m confusing the year, it rewrote the Mail backend to use it and mail hasn’t had reliable search since.
My memory is that quality was so low that we pushed back the release. With the extra time we did manage to fix enough bugs that it was well received. But internally it was more destabilizing than most releases due to the amount of architectural churn.
> Snow Leopard's stated goal internally was reducing bugs and increasing quality. That is a fact, not marketing.
That being a stated goal is not necessarily contradictory with claims that the release introduced bugs and had quality problems. Fixing bugs can introduce new bugs, or unveil existing bugs that were previously hidden by other bugs. It's quite possible that users like the author encountered bugs in their workflows that were the result of fixing bugs that didn't impact their workflows. It's also possible that they used applications that relied on behavior that was considered bugs in the OS, and thus broke when the bug was fixed.
> If you wanted to ship a feature you had to get explicit approval from leadership and the bar was high.
What was defined as a feature? The first new thing I noticed in Snow Leopard was that Quick Look could now preview Adobe Illustrator files (it was not the case in Leopard). I very much welcomed that, but it doesn’t seem like the kind of feature addition that would clear a high bar.
I ran Leopard and upgraded to Snow Leopard on a 2006 Core Duo MB Pro as well. My memory is very hazy on details, but I had remember no issues at all with either one. It was a difficult time in my life, as I my employer essentially laid everyone off in late 2009 and I spent the next 18 months unemployed. During that time my Mac was an utterly reliable means of job hunting, studying for certifications, and applying for unemployment.
Not long ago, a friend of my dad was showing me his old Macbook Pro (one of those big 17-inch aluminum ones). He never upgraded the OS and somehow Safari can still open his email and he has Word and stuff.
That thing was running soooooo smoooth, zero lag, no flickering, no quirks, apps open immediately, etc. That release was peak OS X. I have an M5 Max and it doesn't feel that good.
Tahoe is a massive joke, I downgraded my three laptops to Sequoia and plan to stay there indefinitely.
I remember Snow Leopard as a particularly stable release, but it's been so long this could easily be misremembering. One other thing that was notable about Snow Leopard, though, was that it was the last release before the iOSification of the Mac. Starting with Lion, Apple increasingly tried to unify the platforms and bring ideas and designs from iOS to the Mac, with mixed success.
For myself Snow Leopard holds a special place as the last "pure Mac" release and a culmination of a decade of Mac OS X releases. I skipped over Lion and Mountain Lion, finally getting back on the upgrade train with Mavricks, so I ran Snow Leopard for about four years.
I like how macOS is today, but Snow Leopard was the best version for its time. Also the biggest upgrade was Leopard to SL, biggest downgrade was SL to Lion. So idk what the author's complaint is.
Snow Leopard _did_ focus on stability. It wasn't just marketing. Did new bugs (and even new features) slip in? Yes, of course. It's still an OS made by humans, making imperfect cost-benefit calculations on how to mitigate risk while providing increased value to the end user.
So to say that some people weren't happy with all iterations of Snow Leopard is par for the course for just about any OS or even software release, and IMO doesn't really change the ethos of Snow Leopard.
56 comments
[ 0.25 ms ] story [ 38.1 ms ] threadAs 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.
Is this true of operating systems for most people?
Personally I’d take macOS from 15 years ago (with security bug fixes and new hardware support, assuming modern apps still worked, but no new features) over today’s Windows any day.
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.
haha that‘s a nice nostalgic image. I remember installing it on a friend’s laptop with my DVD in a café, to „fix her macbook“.
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.
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.
https://blog.rongarret.info/2009/08/snow-leopard-is-disaster...
Consistent with this article's take on the situation 17 years later.
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.
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.
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.
People had difficultly opening the plastic case it came in. I did. Ms added a red pull tab to indicate an affordance, then later changed the case to a simple clam shell for Windows 7.
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.
To me the myth is the “no new features”. Apple may have said that in places in marketing but there were new features. Grand Central Dispatch for example.
But in the legend that fact is lost.
Tiger and Leopard were sprawling releases. Tiger covered 32-bit and 64-bit PowerPC, then 32-bit x86, then 64-bit x86 Macs. Tiger was also what I guess I'd say is the first "modern" OSX release, with subsystems like launchd and a more mature OpenDirectory replacing older NeXT subsystems.
Leopard in my experience was a train wreck. It shipped a lot of new features, both user facing and back end frameworks, but the development was seriously impacted from teams losing engineers to iOS. Leopard had features planned assuming 100% availability of SWE's resources but ended up with 40-50% of SWE's resources (made up numbers based on my feels at the time). Many new frameworks in Leopard did not land or get stable until very late in the development cycle which meant everything downstream had to scramble right before GM. It was 100% the case that Leopard was not really stable until 10.5.8 and still sucked IMHO.
There was a lot of clean-up needed in MacOS and that was Snow Leopard. It was not a perfect release but 10.6.3 (the second disc pressing IIRC) and onward were very stable. Dropping PowerPC support really helped focus QA since they didn't need the massive array of test hardware Tiger and Leopard required. You also didn't need to wrangle builds for four architectures, including multiple compilers as a few libraries (if not whole frameworks) were compiled with ICC on x86 for performance reasons.
The "Snow Leopard wasn't that great" meme is weird. I'm sure it had its problems like every OSX release did. Unfortunately most OSX releases broke someone's workflow[0]. Snow Leopard ware no different. But it was always billed internally as a "no new features" release and those features that it did ship faced a very high bar to get in the release. I definitely look back on Snow Leopard as a high water mark for macOS quality in terms of a release.
[0] https://xkcd.com/1172/
There was something else going on during that time period though.
Consumer operating systems in the 1990s were pretty bad. Windows 9x and MacOS Classic didn't even have protected memory. They crashed a lot.
Microsoft fixed this with Windows NT (delivered to consumers as Windows XP), Apple with BSD/NeXT (delivered as OS X). It was the point when ordinary people first got computer operating systems that were fully baked. But the earliest versions (Windows NT/2000 or NeXTSTEP/OS X pre-Snow Leopard) still had the problems that come with new code, so the later releases were better. Hence, the best version of MacOS was Snow Leopard and the best version of Windows was XP (or, depending on who you ask, 7). Because that's when they finally made a decent release.
Once we had operating systems that do essentially what operating systems are supposed to do, since then it has felt like nothing but lateral moves and deterioration because there wasn't much left on the table for newer versions to win but every update is another chance to break or lose something we used to have.
I agree with you that Snow Leopard was billed as no USER VISIBLE features. But people did NOT just fix niggling bugs, it was an architecturally huge release. E.g., it introduced GCD. And unless I’m confusing the year, it rewrote the Mail backend to use it and mail hasn’t had reliable search since.
My memory is that quality was so low that we pushed back the release. With the extra time we did manage to fix enough bugs that it was well received. But internally it was more destabilizing than most releases due to the amount of architectural churn.
That being a stated goal is not necessarily contradictory with claims that the release introduced bugs and had quality problems. Fixing bugs can introduce new bugs, or unveil existing bugs that were previously hidden by other bugs. It's quite possible that users like the author encountered bugs in their workflows that were the result of fixing bugs that didn't impact their workflows. It's also possible that they used applications that relied on behavior that was considered bugs in the OS, and thus broke when the bug was fixed.
I mean, what software is bug-free? Fewer bugs is a big deal. Less-severe bugs is a big deal.
What was defined as a feature? The first new thing I noticed in Snow Leopard was that Quick Look could now preview Adobe Illustrator files (it was not the case in Leopard). I very much welcomed that, but it doesn’t seem like the kind of feature addition that would clear a high bar.
Not long ago, a friend of my dad was showing me his old Macbook Pro (one of those big 17-inch aluminum ones). He never upgraded the OS and somehow Safari can still open his email and he has Word and stuff.
That thing was running soooooo smoooth, zero lag, no flickering, no quirks, apps open immediately, etc. That release was peak OS X. I have an M5 Max and it doesn't feel that good.
Tahoe is a massive joke, I downgraded my three laptops to Sequoia and plan to stay there indefinitely.
For myself Snow Leopard holds a special place as the last "pure Mac" release and a culmination of a decade of Mac OS X releases. I skipped over Lion and Mountain Lion, finally getting back on the upgrade train with Mavricks, so I ran Snow Leopard for about four years.
So to say that some people weren't happy with all iterations of Snow Leopard is par for the course for just about any OS or even software release, and IMO doesn't really change the ethos of Snow Leopard.