I don't mean a situation like that. What if you just disagree about the best way to achieve the ideal ecosystem? Surely not every customer has the same opinion.
Like for example, consider their restrictions on third-party browser engines, JITs, etc. Are you happy about all those choices too?
I would have to think about it honestly, I don't know what I think.
It's a little funny because I think someone reading my comments absent context would think I don't care about general purpose computing. I do care about it though, a lot. I think the centralization of communication services behind a few megacorporations is a sad outcome and a lost promise of decentralized communication between users on the net.
The issue I have is the inbetween - in 'the world as it is' at least apple has leverage to stop the shittiest data mining, tracking, email harvesting, call-to-cancel retentions, just general user hostile 'features' on our behalf. If they don't have that leverage, we don't suddenly gain a better environment - we're in the same shitty centralized thin client world, but now it's worse. In the idealized world of decentralized applications or strong data protection legislation I'd be in favor of it, but in our world I think the tradeoffs are serious and its one of the main reasons I buy Apple hardware.
I don't own an IPhone, so I can't say I'm happy or not about these choices, but at the very least they're not trivially wrong.
Forcing the ecosystem to use shared libs for common, expensive taks like browser engines, JITs, etc, has clear benefits in terms of storage and battery life.
Exactly: they might make decisions which are not strictly wrong, but make the platform less useful for certain people/use cases. Eventually you might find that your most important (although niche) use cases have been killed in a death by 1000 cuts, and they specifically disallow any kind of workarounds.
Like for example, consider their restrictions on third-party browser engines, JITs, etc. Are you happy about all those choices too?