Been there done that. A real solution would be to stop hiring new developers, to reduce the size of the current dev team, to reduce the size and responsibility of the QA team in order to force developers to test their own code. To eliminate any new feature requirements, to prioritze regression testing (migration, update, etc) and to allocate a whole release to trim the pile of bugs in radar. Why Apple can’t do that?…
Really? I've never experienced that in the workplace. However, I'm not that widely travelled and not in SV, so I guess I'd be "unsurprised but depressed" to learn that this degree of idiotic entitlement is common. And idiotic is exactly what it is: truly quality software is the product of lots and lots of bugfixing. It's like the "10% inspiration/90% perspiration" thing, but for initial development and bugfix/gradual improvement work. Especially on huge (OS-sized) software, people hiring on should not be surprised that this is the bulk of their day-to-day.
I get that greenfield development is more fun up front. I just (perhaps naïvely) hope that most professionals understand that a) "fun" and "good for the product" aren't the same thing, and b) that it can also be very personally rewarding to spend a long time fixing bugs (yours or others') and see the quality of/user happiness with a product noticeably increase.
Also, I think being able to say "I fix bugs to maintain an operating system used by millions" is at least as rewarding as being able to say "I make buggy websites for startups whose marketing buzz reaches millions".