News for hackers. Stuff that matters.
Re:Rust Port of TypeScript (Tsc) by aka-rider on Thursday October 08, 2026 @04:15AM (#50003147)
GC doesn’t affect performance (at least visibly), memory allocations on critical paths do. Moreover, Rust ARC may cause memory fragmentation and perform worse than a GC.

Writing Rust, Zig, or Go, you would still control memory manually, where it matters.

Re:Rust Port of TypeScript (Tsc) by dwattttt on Thursday October 08, 2026 @04:47AM (#50003384)
It does have an impact. Discord blogged about unavoidable GC delays in go that occurred because go needed to traverse live memory, their only option (in go) for reducing that pause was to reduce the size of their data set.
Re:Rust Port of TypeScript (Tsc) by legulere on Thursday October 08, 2026 @09:15AM (#50005462)
That seems like a latency rather than a throughput issue. In compilers I would expect latency to be a lesser problem.
Re:Rust Port of TypeScript (Tsc) by sreekanth850 on Thursday October 08, 2026 @05:19AM (#50003606)
https://discord.com/blog/why-discord-is-switching-from-go-to...

GC absolutely has performance costs, even with minimal allocations, because tracing collectors must scan live objects. This is exactly what this post says. Don't know if its really improved over time in real world cases.

Re:Rust Port of TypeScript (Tsc) by aka-rider on Thursday October 08, 2026 @08:13PM (#50014255)
Makes sense.