← Back to context

Comment by overfeed

5 days ago

> It's only a matter of time until it becomes too confusing and problematic to try and run the same system relatively openly in one country and walled in another

They will continue to do so for as long as it remains profitable. Navigating the complexities of multiple jurisdictions is the bread and butter of MNCs - it's the price of admission into the multinational club. Apple is guaranteed to have lawyers, admins, and executives already on the payroll for this task.

Or until they’ve successfully “demonstrated” that it always was impossible.

> Apple is guaranteed to have lawyers, admins, and executives already on the payroll for this task.

As both a shareholder and user, I really wish they’d invest their resources into feature development instead of manufacturing obstacles.

Lawyers, admins, and executives, sure. But what about the complexity on the engineers who now have to maintain an exploding matrix of modes? I can definitely see that becoming burdensome.

  • much has been written about the deteriorating quality of iOS.

    There's bluntly not strong external evidence that software quality is a driving priority at Apple in recent years, so it most probably follows that concerns about maintainability aren't either.

  • You’re not wrong, it is burdensome but the sheer volume of money they secure primarily because of their license to rent-seek mercilessly (in the US especially because it’s the market they dominate most and with the weakest regulators) makes even a hilarious amount of complexity supportable. Besides, it’s mainly the users who suffer from the codebase falling apart, not Apple decision makers.

  • Engineers say they want to work on hard problems then complain that they can’t solve something because it’s too complex

    • The difference is this isn't an inherently hard problem. It's just stupidity. The difficulty is not inherently interesting, because it's all made up.

      1 reply →