3 ms·
All those are just ways to avoid actually using the GC. Which proves the point: GC is ineffective and works best when not used at all. The future is not garbag
by otabdeveloper4 6y ago
All those are just ways to avoid actually using the GC. Which proves the point: GC is ineffective and works best when not used at all.
The future is not garbage collected.
- ogogmad 6y agopjmlp's point is that GC can be the default, and manual memory management can be used where necessary. It's essentially the Pareto principle. Most of your garbage is generated by a minority of your program. So only small bits of your program need to be optimised to not use the GC.
- deleted 6y ago[deleted]
- pjmlp 6y agoYes that is what anti-GC crowd tends to sell, except that it the same set of capabilities that languages like C also offer, with the difference that use after free and leaks abound. The future is pretty much GC with affine types, even Rust has to deal with crude RC<RefCell<>>, without the corresponding tracing GC performance, when doing GUI applications.