3 ms·
My uninformed hunch: There's likely a lot to be said for 1) requiring all apps to use a single modern GUI toolkit, and 2) optimizing that toolkit for the use ca
by epistasis 6y ago
My uninformed hunch: There's likely a lot to be said for 1) requiring all apps to use a single modern GUI toolkit, and 2) optimizing that toolkit for the use case of touch. Rather than having a single codebase that's supposed to solve all use cases in addition to 30 years of baggage.
- gowld 6y agoMost of it is running a single app at a time, with far less complexity than a desktop system.
- saagarjha 6y agoNote that at any given moment there's usually a couple dozen daemons running in the background on iOS. And while iPhone will only show one app at once, iPad can do a handful.
- MarkyC4 6y agoiOS optimizes here too, by limiting how much CPU/IO background apps can use. It's frustrating to use Chromecast (for example) on iOS since it's always disconnecting from the receiver.
- saagarjha 6y agoI'm talking about background daemons from the system, which have different resource limits.
- why_only_15 6y agothe background daemons are mostly memory-limited, not processor-limited.
- saagarjha 6y agoFair. And to be honest, many of them are present on macOS too, without Jetsam around to kill them ;)
- hinkley 6y agoApple fires a lot of customers as well, to stay focused on a narrower set of problems. And we spend a lot of time on the internet complaining about that (nobody likes rejection).
- Razengan 6y ago> optimizing that toolkit for the use case of touch. iPadOS seems to be good enough with mouse pointer and keyboard input too now.