3 ms·

Here's already another platform that does just fine with sandboxing. It's been running for 27+ years. It's called a the web browser. Restrictions against using

Here's already another platform that does just fine with sandboxing. It's been running for 27+ years. It's called a the web browser. Restrictions against using private APIs.... you can't call any private APIs, it's impossible. Find an exploit? It's generally fixed in a few days. Software isn't even installed, new versions are downloaded daily or more so the concept of sandboxing as been throughly tested and proven effective for those 27 years.

Karunamon 6y ago
The difficulty with that argument is that Apple has gone out of their way to make webapps second class citizens. PWAs can't do everything installed apps can. And that's before we get into resource usage.
- arsome 6y ago
  But that's not the point - the point is, sandboxing largely solves these issues without the need for restrictions on side loading, restrictions to a single app store or similar abuses of consumers rights. Apple should build a better sandbox, the idea that "private APIs" exist and the only thing stopping them from being used is a basic string search on the app store review is pretty horrifying.
uberduper 6y ago
You can't be serious.
wruza 6y ago
And then you notice that your browser demands almost the same amount of resources as a 60+fps 3d game for presenting you a just a bunch of static images and some text. It is apples to oranges comparison, because a performance requires an unsandboxed, non-emulated native env, which is hard to protect from exploits. Replace a browser with any OS in existence and see how secure it is to execute an arbitrary binary on it.
- saagarjha 6y ago
  > performance requires an unsandboxed, non-emulated native env Nope, sandboxing is largely orthogonal to performance.