On Wednesday, 12 January 2022 at 16:17:02 UTC, H. S. Teoh wrote:
Depends on what kind of games, I guess. If you're writing a 60fps real-time raytraced 3D FPS running at 2048x1152 resolution, then *perhaps* you might not want a GC killing your framerate every so often.
Resolution is down to GPU performance, raytracing ditto. Realtime GC is a thing (not for d, of course); consistently sub-millisecond pause times are achievable. Given 16ms frametimes (you mention 60fps), that seems reasonable.
(But even then, there's always GC.disable and @nogc... so it's not as if you *can't* do it in D. It's more a psychological barrier triggered by the word "GC" than anything else, IMNSHO.)
Agree.
