Earlier quoted context omitted.
Apple’s blanket ban on interpreted code is not arbitrary. It is there to prevent apps circumventing the review process and security model ie. apps pretending to do X during the review process and then doing Y when in use or obfuscating their use of private APIs. Now you can argue these restrictions are unreasonable but many of us don’t want our iPads or iPhones to be like our computers.
> many of us don’t want our iPads or iPhones to be like our computers And many of us do . I would never buy a locked-down piece of hardware like that. But I don't think it matters either way what either side wants, because it's what Apple wants that matters. They want to keep their walled garden's walls air tight, and there are apparently enough people that are OK living in that garden that it works. I'm positive tha…
Maybe developers could stop looking at the green grass on Apples side of the fence and bring that polish to open-source.
But I imagine that will simply devolve into the mess it already is, with flame wars, and figurative genital punching to prove how hardcore one is for the obfuscated C they cobbled together.
There was time when Linux distributions were thought of as walled gardens. Cobble together just the right collection of source for you! Don’t let Red Hat control your mind! SystemD is a cage for your soul!
Meanwhile, Apple just got the damn job done and moved on.
If it’s a choice between masochistic elitism or filtered content. Hmmm…