The inclusion of integer overflow checks in the slippery slope section didn’t resonate with me. I get that the linked piece was about performance, but I don’t think checking for overflow represents “waste”.
TFA is interesting, but imo it goes too far in the other direction. TFA proposes spending more time on optimization, but really what his examples seem to point towards is just not being careless.
Well worth reading. Also lots of good comments on it!
Reducing resource use isn’t just the right the to do for the user, it is the right thing to do for humanity. As stated, a large number of small numbers is a large number. When you start thinking about resource usage in the large, you start to realize that computers contribute to global warming and it is our job as people not to contribute to the destruction of our own species.
I use languages such as C++ for most of my work for this reason. I am excited about languages such as rust and other type safe languages because if you can prove there won’t be an integer overflow or a buffer overflow, you won’t have to add checks for them (which waste resources).