Again and again Apple's much criticized design choices turn out to be the right ones. In a resource constrained environment, AOT compilation and reference counting get you to a fairly high level of performance and good levels of abstraction with enough simplification for the programmer's task, but without taking too much away from UX in the form of lag.
Mobile is always going to be resource constrained for the same reason highways are always busy at rush hour. Such resources are too valuable to stay unused for long.
(Dalvik will never go to ref counting, but the design trade offs in its GC will reflect the same goals.)
Mobile is always going to be resource constrained for the same reason highways are always busy at rush hour. Such resources are too valuable to stay unused for long.
(Dalvik will never go to ref counting, but the design trade offs in its GC will reflect the same goals.)