3 ms·
The elephant in the room of functional languages is that they all, somehow, fundamentally depend on garbage collected memory management. This GC is never coded
by ncmncm 8y ago
The elephant in the room of functional languages is that they all, somehow, fundamentally depend on garbage collected memory management. This GC is never coded in the functional language itself. Why? Because functional languages are very, very bad at resource management.
Real programs typically need to manage resources besides memory. So, they look good depending on GC for toy problems, but fail to graduate from their sandbox.
The only powerful languages not dependent on GC are C++ and Rust. They have facilities to manage any resources needed, and that are equally adept at managing memory.
As a consequence, it is possible to write libraries for these languages that can work in any program.
Programs in obligate-GC languages always need to compromise some aspect of GC to be practical, but that makes them incompatible with the majority of libraries. Thus, you don't see good library ecosystems grow up around them.
A functional language that did not depend on GC could be useful, but academics would kneecap it immediately. Academia absolute detests the idea of non-obligate-GC languages, for purely tribal reasons.