You know: my heart agrees with this, but over and over I see 'managed' systems exhibiting substantially longer startup times, unexpected and sometimes-long free

You know: my heart agrees with this, but over and over I see 'managed' systems exhibiting substantially longer startup times, unexpected and sometimes-long freezes, and often visibly lower performance. Similarly, virtual memory backed by paging to a swapfile is the beautiful, "right" solution to me intuitively for a memory architecture that is made of several storage classes of highly different access times; yet, I have to admit that hourglasses/beachballs aren't a part of most "mobile" systems but often are — frustratingly — part of the desktop OS experience. In actual practice, there's very little unchecked pointer arithmetic in a Cocoa [Touch] app — you don't access the elements of an NSDictionary via direct (to you) pointer arithmetic but through well-tested methods that fail similarly to how to out-of-bounds collection access fails in managed systems. Anyway, it's unfortunate that such things are essentially non-comparable in a scientific way to my knowledge; but my experience of ObjC apps is not that they tend to be more crashy or likely to corrupt my data than the Java/C# apps that I also use day-to-day.