3 ms·
Why does having. GC mean not thinking about memory? I think about memory constantly in GC languages because I still want it to perform well. The biggest differ
by wild_egg 3mo ago
Why does having. GC mean not thinking about memory? I think about memory constantly in GC languages because I still want it to perform well.
The biggest difference is the failure modes. If I'm not thinking about memory, my RSS is higher or a bit of extra CPU time goes to GC. Both of those are radically better than UAF or buffer overruns. Good trade IMO.
- tjoff 3mo agoI didn't say that. But if you think about memory then GC does more harm than good because you have no help from the language. A GC is not the only fix for UAF and buffer overruns...
- pjmlp 3mo agoDepends very much which programming languages we're talking about. There are enough managed languages with knobs allowing to do C like coding when required to do so.
- tjoff 3mo agoWhich is about as convenient as opt-in types in python. Nice to have but but a poor substitute and requires much more diligence than if it was designed for it in the first place.