Space leaks in Haskell are like memory leaks in a reference-counting garbage collector: a real problem, but one that is manageable. It does not mean we should a

Space leaks in Haskell are like memory leaks in a reference-counting garbage collector: a real problem, but one that is manageable. It does not mean we should abandon all hope and go back to exclusively manual memory management! It's also a problem that tends to be exaggerated and is certainly not a reason to abandon laziness as others (not you) in this thread have suggested. The equivalent of full-on garbage collection would be perfect, of course, and we'll get there eventually for non-strictness and meanwhile the existing system and tooling is improving all the time. Finally, I think people also overestimate how much these things affect the popularity of a tool. I remember having pervasive, hard-to-track memory leaks in JavaScript just five or six years ago, and look how far it's spread by now!