Marco's article seems a little hyperbolic since as I recall Leopard for instance was hugely unstable on release. Conventional wisdom with OS X has always been

Marco's article seems a little hyperbolic since as I recall Leopard for instance was hugely unstable on release. Conventional wisdom with OS X has always been to wait a few point releases before jumping in. With Microsoft it was to wait until at least SP1. I don't think things have changed that drastically. * SMB support still sucks. * OS X Server is still a monumental turd and I wouldn't be surprised if Apple kills it a release or two down the line. * Yanking Spaces in Mountain Lion and going to Mission Control followed by Yosemite finally getting (flaky) multi-monitor support is classic Apple focusing on the consumer before the pros. * Active Directory in Yosemite is a bit buggy but anyone who's used Leopard will remember that the gold master wouldn't even allow AD logons if your domain was .local - I mean did anyone at Apple even test something as basic as that!? It goes on, but I honestly don't think Apple have changed for the worse. They're not any better in my personal opinion either. The biggest problem we face with Apple at my company and it could certainly create the impression of increasing bugginess, is that Apple's release cycle is much shorter now. No more 18 month releases with $100 upgrade fees. Every developer in our shop can click 'Upgrade' on their machine and fuck their whole environment up. It used to be much harder for them to do that in the past which goes back to my original point. Don't upgrade a production machine until you're at least a few point releases in! (that goes for your iOS devices too...)