Most software engineers think about problems in bureaucratic (object-oriented) ways and not in formal ways, because they have been ruined by their "training".
Once they have a job, they discover that convoluted OO code bases offer great job security, so nothing will ever change.
Usually comments that complain about downvotes are downvoted. Have another go, perhaps you'll reach -20. If you persist, you will be eminently qualified as a Wikipedia admin.
Perhaps don't put your system in the path of a proton beam? I've had a large test suite that consistently used 8GB running for three years without ECC RAM. Any bit flip would have been caught by the test suite. My conclusion is that bit flips are entirely exaggerated (probably by the hardware industry for obvious reasons).
WWII had a cohesive effect on the American society and economy that lasted approximately until the 1980s. The results were more equality and less fragmentation during that period.
Since the 1980s technological progress and also social factors brought an ever increasing re-fragmentation, which, if not properly addressed, might lead to problems soon.
Acknowledging these problems is remarkable -- I think it's the first time pg did that.
The current design is closer to the original design. Wait a couple of years, and the design you like will be back. Everything goes in circles for the reasons other people have mentioned above.
The process of creating cross links in one's mind that are actually still available when not staring at google.com works far better when in sitting in a library and reading actual books.
I think science (as opposed to hype like "big data") will progress faster again once the Internet goes out of fashion.
I think Python is a good language, but not for learning.
Everything that relates to theory (scoping, object system, typing) is poorly specified and has loads of special cases that can only be understood by using the language a lot.