Just to be clear, you're suggesting they dedicate $25B/year to bug fixing? Seems high, given their total R&D budget for 2018 was only ~56% of that.
https://www.macrumors.com/2018/11/05/apple-2018-form-10-k-hi...
The spending doesn't have to be instant either. Just start increasing the spending and measure user satisfaction and bug report counts. Once you've arrived deep into diminishing returns you can stop increasing the spending.
How do you know they're not there now? It's hard to believe they're not thinking very carefully about these sorts of things, given how successful they've been establishing a place in the market.
I don't know for a fact but I have more respect towards Apple than to think that the current state is the best they could do.
$265B in Revenue and and $59B in profit seems to indicate they're already doing pretty well. Maybe your definition of 'best' isn't in perfect alignment with the rest of the marketplace?
I get that there are things about their products you can point at and wish were done better, or at least differently. I use Apple products myself, so I have a list of these things myself. But, the thing is, this isn't unique to Apple. Have you ever been completely satisfied with a product or service? I can't really say that I have. About the best that I've ever been able to achieve is something that's a close enough approximation to my 'requirements' that I can adapt what I'm doing to make it a solution.
Point is - you're never going to find something perfect. There will always be a gap and hopefully effort on both sides to close that gap. Those financial numbers aren't a perfect indication by any means, but they do signal that Apple's doing a reasonably good job of closing that gap for a reasonably large number of people willing to part with their earnings to buy Apple's products.
Can you provide a link? I'd be interested to read how it played out. My gut reaction is that number of people logging into Apple's site from Linux is a tiny fraction of their market. At first glance, it doesn't seem surprising to me that they'd prioritize other things.
> How many bugs like that go unaddressed even though someone has spent the time and effort documenting and submitting it?
I'm not sure I agree with the implicit assumption you seem to be making that spending time and effort documenting a bug entitles you to a call on a development organization's resources, time, and prioritization.