> It's just that Apple aren't going to spend their time and money developing software to let you do things they aren't interested in. Why should they?
They are spending time and money to prevent that. Or you can create an app store as an app and expect Apple to allow your "app store app" to ship in iPhones?
The features are already there in the OS, they use them themselves. They dont need to do anything more.. but instead they work to cripple or prevent others from using it.
This is in essence the spirit of a monopoly.
Ok you personally dont mind for whatever reasons, but there a lot of other harms to the society and civil rights in general going on here. And that was the reason countries and laws exists.. To prevent people or companies in position of power to abuse their power.
But there's a specific consumer safety reason for it.
Not letting other browsers use their own JS engine (which is what it means to 'forcing them to use Internet Explorer engine on Windows' in your analogy) is because Apple want to disallow write|execute for people's safety.
Not letting other browsers use their own JS engine (which is what it means to 'forcing them to use Internet Explorer engine on Windows' in your analogy) is because Apple want to disallow write|execute for people's safety.
Perhaps you're right. Maybe it's entirely coincidental that Apple's policy also prevents owners of Apple devices from using a browser with modern features that would allow web apps to effectively compete with the native apps from which Apple gets a huge cut of the revenue because of its monopoly control over the app store.
Granting dynamic-codesigning exclusively to JavaScriptCore shows a lack of confidence in their platform sandbox and the app store review mechanism, and a (occasionally dangerous) overconfidence in the quality of WebKit's security.
But if its because of safety, why only JavascriptCore VM allow write execute flag?
If that was the real reason then, dont you think it should also be disabled in JavascriptCore?
Or the real reason, is as it was pointed out in the other comment, is to cripple other browser engines that offer a platform that could actually be competitive with AppleKit's turning their control over the App store (and what people are allowed to access according to their own taste) irrelevant?
And if that's the real reason behind it, its clear the end user best interests are not being taken into account, as in not having access to possible better options according to your own tastes, contrary to what a lot of people in the comments here are trying to make we believe its true.
Use it as a hammer for all Apple care.
It's just that Apple aren't going to spend their time and money developing software to let you do things they aren't interested in. Why should they?