> You don't see how running any code you want on a device is less secure than restricting the kind of code that you can run?
Who's Apple to decide what I consider to be secure or not in my own free will, on my device? It's like saying that guys from Ford have the right to chime in whenever they want and tell me I can't drive my Ford-branded car to a given supermarket chain.
> Who's Apple to decide what I consider to be secure or not in my own free will, on my device?
They're deciding what is secure on their platform that they can be held liable for. Once you buy an iPhone, you can do whatever you want to it. You can hack it, you can smash it with a hammer, you can submerge it deep underwater. There's absolutely no one restricting your free will in any way here. What you are doing is, of your own volition, purchasing a device that you know has software that has built in restrictions, that you may or may not be able to bypass, but it wasn't designed to be, and getting upset that it doesn't behave as it wasn't promised.
The car analogy doesn't hold up. It'd be more akin to buying a car with android auto and being really upset that it doesn't run apple carplay.
Who's Apple to decide what I consider to be secure or not in my own free will, on my device? It's like saying that guys from Ford have the right to chime in whenever they want and tell me I can't drive my Ford-branded car to a given supermarket chain.