>> consumes a lot of computational power—up to 10 percent or more of the total time a CPU spends on an application.
I stopped reading there. 10% is nothing. For such a useful feature as automatic garbage collection, for the vast majority of applications, I'd gladly give away 50% of the CPU.
In terms of ensuring code correctness and robustness, if I had to choose static typing or automatic garbage collection, I'd pick garbage collection every time. It adds a lot of value in terms of development efficiency and code simplicity.
This is surprising considering that SQLite is very heavily tested. It shows that ridiculous amounts of testing with 100% coverage of every code path and "millions and millions" of test cases still doesn't guarantee that the program always works as intended.
I think that this is an important lesson about testing. We should have fewer tests but we should try to get the most value possible out of each one and for developers that means actively seeking out unusual edge cases that are likely to break things.
This story highlights just how blurry and complex things can get.
Maybe to a lesser extent we are all slaves of the system because we have to work increasingly long hours for an ever decreasing wage.
I think that the most kind-hearted and generous people tend to slowly slip into slavery over time because the system tends to reward greedy, selfish people.
The sudden, massive collapse of the system will come when there won't be enough altruistic, productive people left to support all the greedy, non-productive ones which are currently winning the game of natural selection.
I stopped reading there. 10% is nothing. For such a useful feature as automatic garbage collection, for the vast majority of applications, I'd gladly give away 50% of the CPU.
In terms of ensuring code correctness and robustness, if I had to choose static typing or automatic garbage collection, I'd pick garbage collection every time. It adds a lot of value in terms of development efficiency and code simplicity.