Memory Management Reference (opens in new tab)

All that shows is that, theoretically, one can come up with a system in which generational GC is counterproductive despite a high infant mortality rate. That is not an argument that generational GC is a bad idea in practice, and the article is clear not to make that argument.

That's a limited view. One could very well make it's own class with malloc()/free() in the constructor/destructor, without exposing any pointer like interface. This can be done without reference counting, contrary to what the faq suggests.

the C++ STL takes away the burden of 'hard to implement'. It's definitely hard to do right, but the STL has solved that problem.

I'm sure garbage collection has it's place and use, but the site seems a bit biased against alternatives. Garbage collection definitely has it's scaling challenges for large code-bases.