He is right. He is right about premature optimizations and also right about craftsmanship. Many performance problems stem from bad overall design decisions, b

He is right. He is right about premature optimizations and also right about craftsmanship. Many performance problems stem from bad overall design decisions, bad abstractions and bad data structures (summarized: craftsmanship). I always wonder, how fast today's processors have become and how slow they get with today's software. One of my first computers had 64k of memory and a processor that was so incredible slow compared to today's processors, that it is unbelievable. And still, they made so many good software with it. In today's programs the resources of this computer would not suffice for the idle loop. Also the first Unix computer that I worked on, had only 8MB of memory and had X11, LaTeX and many other stuff! It was a long way down the road of abstractions, that today's computer could hardly live with 1GB of memory and 1GHz processor (2 cores, please, please!) for basic usage. The real art in computer science is, to know where to optimize -- to use your time most effectively.