I don't think you're catching the basic premise here. Brent is suggesting that when you're writing code targeting iOS or the Mac, the majority of time spent is within the system libraries (in most situations). So the language of the driver code (i.e., your stuff) doesn't have much impact on app performance.
You're correct, and that's the same excuse Ruby and Python advocates use when developers complain about performance. Frankly, it's bullshit.
Take Rails as an example. In 2006 we were told that Ruby's slowness didn't matter since web apps spend most of the time waiting for IO, processors were getting faster, yada yada yada.
Guess what? 10 years later and Rails is still slow. Django is also slow. Template rendering is slow. I've written enough Erlang, Clojure and OCaml apps to know that no, I don't need "russian doll caching" in a fast language. Hell, I rarely need caching at all. My database layer is fast enough. /rant
I'm Django developer and I agree with you. We've ditched Django templates entirely. We use it as our API platform only - most of the computation time is spent in json and in Postgres.
>, the majority of time spent is within the system libraries (in most situations). So the language of the driver code (i.e., your stuff) doesn't have much impact on app performance.
Is this really true or is it a perception based on being in whatever respective bubble filter we're in? E.g. if one is an Apple developer for a corporate backoffice, one does CRUD stuff on iOS. But if one is not in that situation, one thinks performance matters.
... one sees a lot of games and some image manipulation apps (facetune, faceswap, video editor, etc). These types of apps require tight loops outside of system libs and performance tuning. I see a few CRUD apps on that list such as HotSchedules and maybe the fitness apps which probably don't need ultratight performance loops.
