"So saying "just don't use GC" as a answer to improving throughput shows ignorance." It could also mean they use Rust, memory pools, some kind of checker that

"So saying "just don't use GC" as a answer to improving throughput shows ignorance." It could also mean they use Rust, memory pools, some kind of checker that catches those errors, or separation logic. Probably that order due to popularity. As a counterpoint to "don't use GC," there's also low-latency or real-time implementations of RC/GC to consider as well. A lot of developers using RC/GC languages don't know they exist. Maybe we need a killer app that uses it to spread awareness far and wide. More open implementations of the concept, too.