4 ms·
> They should do it, but I doubt it would cost them nothing. Let's be real here, they just don't want to do it. The cost of the documentation review would be
by oblio 4y ago
> They should do it, but I doubt it would cost them nothing.
Let's be real here, they just don't want to do it.
The cost of the documentation review would be peanuts.
Apple has just broken capitalism, they're probably 5 years away from rivaling Saudi Aramco in profits:
https://companiesmarketcap.com/most-profitable-companies/ https://companiesmarketcap.com/most-profitable-companies/
Financial excuses for Apple strategy decisions don't really hold up to scrutiny ;-)
- alfonsodev 4y agoYou have to consider the opportunity cost, probably those people engineering time is better placed on M3 gpu drivers. It takes really excepcional and kind people to achieve what they did AND prepare public documentation along the way for the profit of open source community. It sometimes happens, and we have to celebrate that more, but it's not the normal.
- oblio 4y agoOr, you know, they could hire good technical writers for a fraction of the cost and have them work together with developers, just like other companies do? Devs would have to write just the hairiest parts.
- alfonsodev 4y agoyep that sounds reasonable, no idea why Apple doesn't do that, my wild guess is that there aren't enough technical writers that can understand low level code, or just a company/team culture that doesn't value it.
- spacedcowboy 4y agoYou speak so blithely, I can see you've never gone through an Apple documentation review...
- oblio 4y agoSpeak less blithely yourself, then ;-)