4 ms·
Also, re: laziness, it's more nuanced than that. See this quote by SPJ, from a 2009 interview ( https://www.simple-talk.com/opinion/geek-of-the-week/simon-peyto
by the_af 12y ago
Also, re: laziness, it's more nuanced than that. See this quote by SPJ, from a 2009 interview ( https://www.simple-talk.com/opinion/geek-of-the-week/simon-peyton-jones-geek-of-the-week/ https://www.simple-talk.com/opinion/geek-of-the-week/simon-p... ):
> "Laziness has lots of advantages, including modularity. These days, the strict/lazy decision isn’t a straight either/or choice. For example, a lazy language has ways of stating ‘use call by value here’, and even if you were to say ‘oh, the language should be call by value strict’ – which is the opposite of lazy - you’d want ways to achieve laziness anyway.
> Any successor language to Haskell will have support for both strict and lazy functions. So the question then is: what’s the default, and how easy is it to get to these things?
> How do you mix them together? But on balance yes, I’m definitely very happy with using the lazy approach, as that’s what made Haskell what it is and kept it pure."
I'd say he is arguing that keeping laziness as the default was the right choice...