Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
10.6.4 is when Snow Leopard did get really reliable. It had some bugs including one big one before that although that particular bug never impacted me.
I guess me not upgrading to iOS 26 asap last year really solidified my belief that I should only upgrade near the end of iOS release cycle.
 
Uh what? They absolutely did. Just because there's staggered release schedules doesn't mean they weren't codeveloped. It's not the same people working on both platforms.
It's not that hard to look at what actually happened unless you're terrified of facts.


Apple on Thursday pushed back the release of Leopard, the next major upgrade of its Macintosh operating system, until October, saying it had to divert too much of its resources to getting the iPhone out on time.​


What does divert mean again?

"We had to borrow some key software engineering and QA [quality assurance] resources from our Mac OS X team, and as a result we will not be able to release Leopard at our Worldwide Developers Conference in early June as planned," the statement said.​


Well, how about that!
 
It's not that hard to look at what actually happened unless you're terrified of facts.


Apple on Thursday pushed back the release of Leopard, the next major upgrade of its Macintosh operating system, until October, saying it had to divert too much of its resources to getting the iPhone out on time.​


What does divert mean again?

"We had to borrow some key software engineering and QA [quality assurance] resources from our Mac OS X team, and as a result we will not be able to release Leopard at our Worldwide Developers Conference in early June as planned," the statement said.​


Well, how about that!
I’ve already explained why you and the other poster are wrong and misunderstanding what resource allocation (something common in software development) is. I’ve already explained that *work didn’t stop* on MacOS which is the crux of the argument.

Stop with your caps nonsense next time and understand what the word “some” means.
 
It is not uncommon that you would cut different builds out when you know they are already planned so that the features planned for those releases can be built and worked in that version. Pretty standard things with software development.
 
If Apple knows what is going in the .4 now and is testing it...why not put all that stuff in the initial release? (I know there will be a reason, I just cant see what it is)
'Cause that release is super duper alpha by now, they're building the future waay ahead and far from what's being worked on now.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.