Comment on: What a C programmer should know about memory
1 25 Jun 2015 17:30 u/icemaze in v/programmingComment on: What a C programmer should know about memory
I could turn your claim on its head and state that explicit memory management is part of the reason software is as buggy as it was in 1997.
Explicit memory management is a form of premature optimization and it's error prone: bugs, sometimes serious security bugs, can be introduced (use after free anyone?). So while it's obvious that my claim is true, you provided no evidence for yours.
Comment on: What a C programmer should know about memory
Thank Knuth for garbage collection.
You did not address my claims. GC is less error prone, and the performance hit is often (not always, but often) justified.
You want proof that manual memory management is error prone? Here it is. Wait, here's some more.
You want proof that GC performs BETTER than manual memory management for SOME (not all) workloads? Here it is
Can you please quit your jihad against GC and try to embrace a more balanced view?