Re:Garbage Collection for Systems Programmers
by zozbot234 on Saturday March 30, 2024 @03:09PM
(#39877672)
Except that obligate ARC ala Swift has even lower throughput than obligate tracing GC. It's the worst possible choice unless you really care about low-latency and deterministic freeing of resources (and even then, using RAII for common tree-like allocation patterns like Rust does will perform better).
Re:Garbage Collection for Systems Programmers
by pron on Saturday March 30, 2024 @03:18PM
(#39877742)
You're right, I should have said "languages where GC is the primary means of managing heap memory are used by 90% of the market" rather than focused on a specific algorithm.
Re:Garbage Collection for Systems Programmers
by ngrilly on Saturday March 30, 2024 @03:23PM
(#39877792)
Yes, this is quite fascinating how GC replaced manual memory management in most apps over the last 20~30 years.
Tracing GCs have clearly proven themselves and are everywhere (JVM, CLR, Go, Dart, OCaml, etc.) but we can't ignore that the Apple ecosystem (Swift) is using ARC. That's a significant share of the "market". Python and Ruby also use reference counting, but I don't think anyone is considering them state-of-the-art GC.