Ya, but they didn't figure that implementations would be so brain-dead. From what I can tell, it's not the protocol that's at fault but how browsers handle OCSP failure. It should be a hard error.
there are many who would classify some building codes as unnecessary and some as absolutely essential, but for others the difference between the two is just too much to fathom... and as a result of their brains hurting so much, or from ulterior motives, they come up with something completely asinine: remove all regulations, they're too hard, and let's just find out what happens!
turns out, most of the time that's actually too much for everyone else to fathom, frankly.
Here's a different take, then, and probably harder to verify, but I am guessing is true:
Cache utilization has increased much more than RAM or HD, not just because programs are handling more data but also because of increases in program size and number of programs being run simultaneously.
Your hard drive is probably not full... RAM could be, depends on your workload... but I bet most caches are churning like mad, more than they used to be.
"modern C++" has changed meanings so many times in the past 10 years that it's not funny anymore. there's always some "modern" solution in C++ that ends up causing more problems, leading to further "modern" solutions that end up... you get my point.
some folks have decided to get off the C++ feature treadmill and go back to, well... getting things done with solid languages (e.g. C) instead of learning about the latest C++ non-solutions to non-problems.