3 ms·
Another tangential but related one is core architectural decisions made early on. Apple wanted to build apps using web technology, but realized it was nowhere
by Cthulhu_ 4y ago
Another tangential but related one is core architectural decisions made early on.
Apple wanted to build apps using web technology, but realized it was nowhere near fast enough. So they reused parts of the OSX toolkit, including the programming language which compiles down to optimized assembly. (and it wasn't even that great in performance due to obj-c's way of doing things, it had more runtime overhead due to the message passing system).
Meanwhile, Android always was on Java and the JVM, which, while pretty fast, isn't as fast or energy-efficient as a lower level language. If I recall correctly it took something like five years - and quadcore CPUs - before Android started to get close to iOS in terms of perceived performance and speed, and the iPhone still beat Android phones in terms of energy efficiency. It took even longer than that (again, if I recall correctly) for the iphone to even start having a dual-core CPU.
And Apple is doing it again with their own CPUs now, the energy efficiency of their new macbooks with no compromise on performance is really impressive.