3 ms·
Jobs didn't want 3rd party software on either the Mac or the iPhone and had to be persuaded to allow it by the rest of the team. Whilst I often wish I could in
by rahoulb 9y ago
Jobs didn't want 3rd party software on either the Mac or the iPhone and had to be persuaded to allow it by the rest of the team.
Whilst I often wish I could install the local development environment of my choice onto my Pro, having seen the crap that grinds all my dad's computers to a halt (he's one of those that sees something and just installs it) the "sandbox the shit out of everything" approach really makes sense to me.
- majewsky 9y ago> the "sandbox the shit out of everything" approach really makes sense to me It's more than just sandboxes. Android grinds to a halt just easily when you install crappy apps. For example, I used a German classifieds app called Shpock for some time. After I uninstalled it, I noticed that I got around 50% more mileage out of my phone's battery. As far as I've heard, stuff like this is not as prevalent on iOS because Apple enforces stuff like background scheduling more strictly than Android does. It's not just the sandboxing, it's the behavior of the interfaces that the sandbox offers.
- hunnefeldtyler 9y agoThis is one of the areas that I really like about Apple, however frustrating it is for developers. There are only a few ways to run (non-finite) code while the app is backgrounded. Android seems to be taking a page out of iOS's book with the introduction of Android O and its restrictions to background services.