> If the ecosystem relies on app inspections that much it simply needs to be secured better.

How do you secure something without inspection? We have health code inspections for restaurants, car safety and emissions inspections, IAEA inspectors visiting nuclear facilities… Should we throw all those out too? What replaces them, the goodwill and word of people?

The ostrich is saying that the technical sandbox controls of the is will still be present.

Those will never be good enough to overcome social engineering.

The OP... The technical controls of the OS...

Autocorrect and a lack of editing are a bad combo.

In this analogy, getting to design the system on which the apps run is something like being able to alter the local laws of physics so that car exhaust simply can't contain pollution.

What I mean is, the OS should not allow apps to do these things. Rather than inspecting the code and strictly banning any dynamic code (one of the reasons emulators are not allowed), the apps should just not be allowed to do things like call hidden APIs at OS level.

They don’t read the code afaik; they prevent memory page being marked both write and execute (with an exception for javascriptcore specifically).

W^X pages are one of the most widespread sources of RCE bugs, and banning them by default is a good idea.

> If the ecosystem relies on app inspections that much it simply needs to be secured better.

How likely is this when Apple aren't getting paid for apps any more? Who should pay for it?

No what I mean is that regardless of the apps that run, there should be no way to circumvent it. The OS should enforce this.

It's not always that simple. What if I make an app that asks for some data from you "for it to function", and then posts that data to somewhere it shouldn't, there's not a lot to be done about that from an OS enforcement perspective.