Earlier quoted context omitted.
> The argument was users should have the ability to run whatever code they want on their iPhones. That is actually possible today. Technically possible, fine. But there's a big gulf between "possible" and "not extremely painful". Let's say I create a personal fork of the open source Bitwarden password manager, to add some trivial quirk that makes the software better fit my life. How do you propose I actually use my c…
It sounds like the problem you have isn't that it's not possible, but that it's not free (as in beer). The free account is good for playing around with the environment and learning how to write code for iOS. It is not well suited for running production software on your phone. If you want to run production software on your phone, blessed or unblessed , you probably want to pay Apple $100/yr for the longer duration and…
But, I also fundamentally believe we shouldn't be restricting user freedoms to protect copyright.
$100 a year is completely and utterly cost-prohibitive for a lot of people, even within the context of someone who already owns an iPhone. A lot of children begin coding so they can create something for themselves, or change one thing in an application. With a 7-day limit, who would want to do that? While it's true that free accounts can technically experiment with coding, there's not much incentive when you can't really _use_ anything you've created.
I worry about a generation of children who is given iPads rather than computers. Sure, most of them would never have touched code anyway, and that's fine. But iOS completely removes the incentive to learn and explore—to actually hack and tweak and create the tools we use everyday, instead of blindly consuming them.