>"and that has always been disallowed".

And it's always been a stupid rule. If I ship an app with a browser view, I can run any custom code I want in it. The rule is just a bandaid on Apple's lack of true sandboxing for apps.

▲

wvenable 14 hours ago | parent | next [-]

> The rule is just a bandaid on Apple's lack of true sandboxing for apps.

That's not it at all. If an app can run arbitrary code then it can run other apps and that can by-pass the app store. They are specifically trying to prevent something like Wechat on the iPhone. It's not about security, it's about money and control.

▲

mciancia 14 hours ago | parent | next [-]

Wechat works on iPhone

	▲	F7F7F7 12 hours ago \| parent [-]
		Wechat is large enough to be able to negotiate requirements with Apple. They are the gateway to an entire continent and close to 2 Billion users. And since they are a 'everything app' the frequency of use and reliance is likely compounded. Apple's not picking up the phone for 50 million users. So we shouldn't expect anything different here. Luckily there are other phones and mobile os's to develop for.

▲

greyface- 13 hours ago | parent | prev [-]

If we had to live with this rule during the "classic" Mac era, it would have disallowed HyperCard.

▲

sheept 14 hours ago | parent | prev | next [-]

That's because browsers are the most battle tested sandbox out there. It's not worth developing another sandbox if they already have Safari webview.

	▲	Jyaif 14 hours ago \| parent [-]
		> browsers are the most battle tested sandbox out there The most battle tested sandbox... after operating system. After all, browsers rely on the OS to provide the primitives for their sandboxes. And curiously those primitives are not exposed by iOS.

▲

wat10000 13 hours ago | parent | prev [-]

What's lacking in the sandboxing?