872 karma · joined July 16, 2012
So far they’ve chosen to go with a simple feature flag but eventually it may require a pullout. Especially if the EU fines them for not releasing features in the EU.
Apple has far more leverage than the EU in this case. Millions of unhappy EU consumers are a much more powerful motivator than a few billion lost in revenue for a company as rich as Apple.
Apple would recoup most of the lost revenue through black market and secondhand sales anyway.
What this could've been is a better way to consume external APIs to avoid the SDK boilerplate generation dance. But the primary problems here are access control, potentially malicious clients, and multi-language support, none of which are solved by this system.
In short, if you're working over a network boundary, better keep that explicit. If you want to pretend the network boundary doesn't exist, then let a data sync engine handle the network parts and only write local code. But why would you write code that pretends to be local but is actually over a network boundary? I can't think of a single case where I would want to do that, I'd rather explicitly deal with the network issues so I can clearly see where the boundary is.
[1] https://bytemash.net/posts/i-went-down-the-linear-rabbit-hol...
Backup power is easily achieved with a UPS, and backup internet connection with an LTE router (or two).
But the feeling of being able to tinker with something physically in your own space? Cannot be beat. You can do so much that isn't possible over SSH, just because it is there.
https://landgeist.com/2023/07/22/skin-cancer-prevalence-in-e...