I guess so. I'm just thinking that the argument often is that Apple has full control over their products since they're the ones behind both the software and the hardware when it comes to their operating systems. Therefore I find it strange there (relatively often?) seems to be pretty obvious bugs and glitches not getting fixed.
But I don't use other operating systems that extensively, so can't really compare the stability in a fair way.
It doesn't matter what the product is or who makes it. Quality is a function of process.
Developers are rewarded for new features. Maintenance, fixing bugs, dealing with test system regressions and writing tests are considered tasks that you have to do along with development. But software engineering companies reward development. So what do you think developers focus on? In the extreme case, you go to a new project, do the development, get your rewards and then move to a new group so that you don't have to do maintenance and bugfixes for the code that you just wrote. That's how you maximize your financial rewards in software engineering. Doing successful new projects also gets you promoted.
If you want better quality, put in the process and the rewards to achieving quality.
In another extreme example, you have a development group develop a feature with no testing or minimal testing. Of course it falls all over the place when someone actually tries to use it. But you get your feature done on time and in the code. You then have to spend a lot of time actually writing tests and then fixing all the bugs. You can reward or punish this behavior but engineering companies tend to reward it from what I've seen. And that's why you generally have crappy software across industries.
But it's the same thing regardless of the product. You could have the same issue with cars, light bulbs or tennis racquets. You get what you incentivize.
eclecticlight.co
