Hacker News Reader

Games, or soft real-time systems (like audio tools; synths, DAWs, or editors). Potentially, cross-platform mobile apps.

Thanks to its approach to GC, you can impose a limit on the time to spend on GC between ticks, so no unpredictable performance stuttering.

I see it as having nice "functional-ish" syntax like Python, but with static types.

View on HN

A limit on GC time might then obviously lead to high or too high memory use, potentially?

Not OP or aware of Nim's specific implementation, but in some cases, yes. However in a fps-sensitive situation like a game, it just takes ~16ms of GC before you've missed at least one refresh. By limiting the time to something lower, we can distribute this time such that the user doesn't notice any stuttering, provided the GC events were spaced out enough.

Reply on news.ycombinator.com