3 ms·
> "It is a pain to fight the compiler over memory, especially coming from a garbage collected background" What I don't understand: why don't people stick with
by singularity2001 7y ago
> "It is a pain to fight the compiler over memory, especially coming from a garbage collected background"
What I don't understand: why don't people stick with garbage collected languages whenever possible?
- pkolaczk 7y agoBecause GC addresses only one type of resource: memory, but there exist many other types of resources, and handling them correctly is PITA in most GCed languages.
- cogman10 7y agoLots of reasons. - You don't want to spend time tuning your GC. - Response Latency REALLY matters - Response Throughput REALLY matters - Memory footprint REALLY matters - Application + runtime footprint matters - Memory isn't the only resource you need to manage - Cost matters I get that you said "whenever possible" but figured I'd list reasons for "not possible" because I think they have a lot of tie in. In particular. I could imagine that cost is going to be a driving factor in the future for people to want languages like Rust. They want the absolute fastest app runtime with the lowest resource footprint because AWS charges you for the more memory and CPU time you consume. In that case, the most economical thing to do is favoring the fastest to start and run languages available with the smallest amount of resources. You might be able to technically do the same job with python, but if you can reduce your operation cost by 10x by switching (or starting) with a slimmer languages, why not?