I haven't had to analyze the performance of no-swap processes before. My assumption is that code is hot enough to avoid eviction and that evicted code pages are rather the exception. To strong-man the argument, I can imagine long running complex (bloated) services could have parts that are not touched unless a specific request comes in.

[1] As used by Jack Dennis and Arvind: https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#... [2] Originally defined by Karp & Miller: https://www.jstor.org/stable/2946247

By adding that, he is implying "Don't need to act, keep burning fossils, tech will fix it". That is in itself asserting a simplified model assumption about a (human) world that is much more complex; something he was railing against in the previous parts of his text. Either it's a cheeky joke, he himself is an intellectual or both.

Now dispell the "this is just the western tradition": do Klingon music theory https://youtu.be/1LjcBv-OWtQ

E.g. In the movie the protagonist glances an office worker that looks like her. The manga has her explain that she looks like a cheap generic model to hide the fact she is full of expensive specialized government tech. I always think of that scene when I put an expensive work laptop in a ratty backpack.

I also grew to understand the value of people digging deeper into the underlying issue, instead of just answering "how do you do X in Y". The usual reaction was "I don't want to explain to you why I want to do it like this. Just tell me how to do this!"