collectors

Also, the abuse already happened, you are only stopping the dumber CP collectors from sharing images of it.

Does that mean childporn collectors are thanking the NSA too?

Copying collectors also gives you memory defragmentation for free, which ensures quick allocation times, something ARC cannot do.

Even within the Oracle/OpenJDK sphere - there are 4 different garbage collectors which all could affect this pattern differently.

Debt collectors and commercial collection attories report to db, skip trace, and have folks trained to find assets and deadbeats.

Compacting generational collectors make allocation very cheap, and they make maintenance of short-lived objects very cheap.

Where GC's have a memory overhead (copying collectors), they do it on purpose, on machines which do have enough memory.

Most languages with garbage collectors also have mechanisms for working with memory that doesn't get touched by the collector, to support FFI.

Marlinspike’s encryption scheme can be applied to imagery, then childporn collectors thank him too.

Those copying collectors are the fastest, but cannot be used on small devices.

The JVM (and I presume the CLR as well) has a couple of different garbage collectors that support concurrent (i.e.

Cable companies are ruthless tax collectors and deeply entrenched in political circles.

I find the methodology of the research to be solid, the collectors to be representative of the different approaches in the field and the conclusions to be consistent with the gut feeling from experience: "With only three times as much memory, the collector runs on average 17% slower than explicit memory management.

Luckily as it happens I am an expert in JVM Garbage Collectors:-).