Earlier quoted context omitted.
I don't view the iPhone and iPad as "computers" or "personal computers" any more than I view my cable TV set-top box or Sonos speaker that way. Both are very powerful devices with Linux operating systems. But I don't expect to be able to program them. The iPhone is an appliance that can download "apps" that Apple permits. When I want a "computer" I open up my MacBook.
> I don't view the iPhone and iPad as "computers" or "personal computers" any more than I view my cable TV set-top box or Sonos speaker that way. Why should your personal view obviate the devices' nature? These are all computers. *Whose* computers is the more important question. And from a look at a lot of these 'narrow focused computer devices' have the company you bought it from still exert control years after your…
The obvious upside is that people who start off building hobby apps may well move into developing apps - and perhaps even associated hardware - professionally.
This is very likely to lead to increased goodwill and significant further purchases of products and other services.
Development of Xcode (not the best environment ever...) and Swift/UIKit will continue anyway. There is no sense in which a few thousand/tens of thousands of hobby developers are paying for that to any significant extent.
This does not require sideloading or loosening the security. It requires a slight relaxation of the provisioning system for single devices - something which exists already.
I don't care what the fanboi justifications are. Not doing this makes absolutely no commercial sense. Apple is gaining a somewhat imaginary $99 a year, which hobby developers won't pay anyway, and losing extra sales of hardware and apps which are potentially worth far more. It's also driving hobby coders towards competing ecosystems.
Instead of expanding the ecosystem this contracts it.