Comment Re:Garbage Collection (Score 2) 85
I can't speak for the experiments you're referring to specifically, but I've seen studies make the mistake of comparing a 1:1 ratio of std::shared_ptr objects to garbage collected references in other languages. I hate these comparisons because it overlooks the fact that garbage collected languages are so enamored by their own GC firepower that they insist on creating garbage all over the place. Outside of the base primitives, pretty much everything becomes an object that is individually tracked on the heap. C and C++ have the advantage of keeping tons of stuff on the stack and having many objects share one block in the heap (pools, regions, etc.) if necessary.
Obj-C and Swift seem to sit in the middle as it forces certain objects into the heap against your will, but I'd still think that just a little bit a forethought in the application's design would allow it to beat most GC equivalents.