51–60 of 152 posts
Terrible book. Please, please read Graham Hutton's Programming in Haskell. LYAH is full of incorrect definitions and broken analogies. Hutton on the other hand is up there with K&R for clear and concise definitions.
Terrible book. Please, please read Graham Hutton's Programming in Haskell. LYAH is full of incorrect definitions and broken analogies. Hutton on the other hand is up there with K&R for clear and concise definitions.
Yeah, it tries to be funny but it's just annoying and disorganized.
Another good (imho better) option is the Haskell book https://haskellbook.com/
LYAH is more appealing for early learners, since it's free.
Still recall the advice form a classmate asking if I should learn Haskell -- he said "Just learn it because it'll change how you think about programming". I think people should learn it for this exact reason -- it really does change how you program as well as thinking about programming even if on a daily basis you're not writing pure Haskell or Clean or Scheme or whatnot. Common programming concepts like "iteration",…
I always think that this attitude is a little bit off. Obviously learning a new paradigm or a new language is great and expanding your horizon is very rarely bad, but I feel a little bit sad about shoehorning Haskell, or functional languages in general, still into this education category. Haskell is a very solid production language and you can put industrial grade software in Haskell out there, and it is in fact used…
Unfortunately there are some places where aspects of the standard infrastructure around Haskell block production application.
In particular, we have applications with very hard latency requirements and also with complex type/binding requirements (where a direct structural type system is needed):
Earlier quoted context omitted.
What would you recommend?
Another entry in the not Haskell category, Functional Programming in Scala is outstanding.
[0]https://www.manning.com/books/get-programming-with-haskellIn addition, the IRC channel was immensely helpful along the way.
Nowadays I just use haskell for a few things at work or for toy projects, and the initial steps were taken with LYAH. (Beginner level though and I think I learned more from irc than the book in the end)
Terrible book. Please, please read Graham Hutton's Programming in Haskell. LYAH is full of incorrect definitions and broken analogies. Hutton on the other hand is up there with K&R for clear and concise definitions.
As unfortunate as that may be, I'm glad to hear that maybe it's not that I can't learn Haskell, maybe it's just that I chose the wrong book. So here's to trying again with Hutton's book!
Terrible book. Please, please read Graham Hutton's Programming in Haskell. LYAH is full of incorrect definitions and broken analogies. Hutton on the other hand is up there with K&R for clear and concise definitions.
"LYAH is full of incorrect definitions and broken analogies." Well it's fine for beginners, because beginners want easy explanations and many examples to start with, instead of very precise definitions which requires a precise math vocabulary.
Earlier quoted context omitted.
I think one of the most important things I learned from functional programming was how to consider and handle purity and side effects. Not necessarily by wrapping everything in IO monads in my non-functional code or anything like that. But trying to keep bits of business logic in pure functions (where possible, of course) sure makes my job easier.
Yeah but you don't have to learn Haskell to understand that