4 ms·
> GC garbage collection in a different "managed" language. The tradeoff is higher RAM footprint, extra cpu and GC pauses for tracing scanners It would hardly m
by kaba0 5y ago
> GC garbage collection in a different "managed" language. The tradeoff is higher RAM footprint, extra cpu and GC pauses for tracing scanners
It would hardly mean a problem for most programs, including OS kernels, especially that kernels are themselves GCs for resources like processes, file handlers, etc.
Also, GC pauses are overblown, most of the tasks can be done in parallel.
- Yoric 5y ago> Also, GC pauses are overblown, most of the tasks can be done in parallel. I've spent a few years writing code that needed to run at 60fps and, well, that's not my experience :)