3 ms·
Whoever came up with this GC will save you from memory management headaches mantra deserves to be quartered. What is even worse is that thanks to a modern progr
by FpUser 5y ago
Whoever came up with this GC will save you from memory management headaches mantra deserves to be quartered. What is even worse is that thanks to a modern programming education however it is done most developers believe in this BS as well.
Sure GC will save one's ass in trivial cases, but few non-trivial become way more difficult to discover.
- not2b 5y agoYes, I've repeatedly encountered programmers who insist that leaks aren't possible in GC languages, and they then build ugly stuff where nothing ever gets freed because a tangle of references connects everything to everything, and they won't even call this situation a leak, even though they have allocated objects that will never be used again that keep growing.
- howinteresting 5y agoYeah, GC inevitably leads to hideous memory leaks. In some cases that's totally fine! For example, if you have a stateless fleet of server-side applications and you can restart any of them at any time, or if you have a CLI that runs for short amounts of time. In other cases, for example long-running stateful servers, games or GUI apps, it can quickly become a real problem.