2 ms·
You're taking issue with material that is covered in every haskell 101 course worth it's salt (how to understand the properties of foldl and foldr). We typical
by platz 10y ago
You're taking issue with material that is covered in every haskell 101 course worth it's salt (how to understand the properties of foldl and foldr).
We typically don't evaluate the efficacy of a language contingent on someone who is missing fundamental, well-known concepts about the language.
Also, I don't think folks "ignore the evaluation strategy for eagerly evaluated languages". They simply learn it early in in their programming experience.
- zzalpha 10y agoYou're taking issue with material that is covered in every haskell 101 course worth it's salt (how to understand the properties of foldl and foldr). Oh, I'm not "taking issue". This isn't personal. It's just my observations. And yes, that one needs to explain the consequences of lazy evaluation and the potential for space leaks to a complete neophyte to justify foldr/foldl is literally exactly what I'm talking about! :) Space leaks are complicated. And they're nearly unavoidable. I doubt even the best Haskeller has avoided introducing space leaks in their code. That's a problem. Are you saying it's not? Because that would honestly surprise me. Furthermore, are you saying eager languages have analogous challenges? If so, I'm curious what you think those are! It's possible I'm missing them because I take them for granted, but nothing honestly springs to mind.
- platz 10y agoI didn't claim space leaks aren't a problem. But one has to size the magnitude of the problem appropriately. And one should also cross-reference that with experience reports from companies using Haskell in production.