3 ms·
Hmmm, I don't find the latter that useful. It's more a "Why we don't use Hackell more" essay, since the problematic things he cites are not present in many oth
by hga 16y ago
Hmmm, I don't find the latter that useful. It's more a "Why we don't use Hackell more" essay, since the problematic things he cites are not present in many other functional languages (pervasive laziness and the sharp delineation of state changing code).
Particularly in the original functional programming language family of LISP (which, I grant you, has been multiparadigm from the beginning). Even in the most functional most successful branch of Clojure things are somewhat friendlier (although it's new enough plenty of practical programming warts still need attention).
It's my strong impression that for a long time Haskell has been as advertised in an "Avoid Success At All Costs!" mode so that various particularly pure things could be explored. The ML family might be more worthy of examination along the lines of the author, particularly with F#'s elevation to first class status in the Microsoft .NET ecosystem.