Besides google's RE2 and writing properly parallelized and cached code, this article highlights the most important thing which we are in the process of losing a

Besides google's RE2 and writing properly parallelized and cached code, this article highlights the most important thing which we are in the process of losing at the moment. Testing your code on low cpu clock and disks with spinning parts. I'm pretty sure if we had this hardware in the 60s, computer science would have halted because people would have thought "oh why bother reducing this algorithm to nlogn where n^2 is computable in a perfectly reasonable time frame for the use cases we have?"