> We hope this material is helpful for you as you work on your own software. Sadly, as interesting as the material in the article is (great to learn about the measured latencies of the hardware part), I fail to see much that is "actionnable" for a run-of-the-mill software developper. It seems the only advice is "don't download ad / tracking / social media - related stuff", but even that is not exactly in the developp…
The author doesn't say you should use a language without GC, but minimize its effects. There are techniques to avoid GC churn by reducing allocations and the subsequent cleanups.
doWork(int x, int y, int z)
they refactored that into doWork(Coordinate c)
and that's when Minecraft started eating RAM like some sort of delicious candy, because now each time you deal with a new Coordinate, it's one more object to garbage-collect. The old method may not have been particularly pretty, but plain ints are allocated on the stack and thus reduce GC pressure.(BTW, can anyone confirm or deny that anecdote?)