>2013 >still using C

Some people, when confronted with a problem, think ``I know, I'll use manual memory management.'' Now they have two problems.

free(ptr);

HOLY FUCKING SHIT THAT WAS SO FUCKING HARD!

My function can't return an array, what do I do!?

>>3
Return a function instead.

In practice, GC is actually faster than its alternatives. MMM means more performance only in the ideal case (see: Nirvana fallacy). Dynamic allocation and deallocation is also subject to crashes and exploitation, which means no one touches it for serious projects.

GC is great if you don't need determinism and you aren't resource limited (i.e. most situations.) Even in the case of being resource limited GC can usually still work.

GC still a shit though.

>>5
Dynamic allocation and deallocation is also subject to crashes and exploitation
If you have a hold of the environment or kernel, and can manipulate what is on RAM. Also that statement is true regardless of GC or determined Dynamic Memory Allocation(IOW, GC uses DMA too).

>>7 has said correctly. And most situations are 99% of the time, unless you really want to have frequent reboots and crashes.

>>3 or loops.

GC is actually faster than its alternatives
It's faster only until it has to free something.

Then performance goes to hell.