Introduction

[[deleted user]]

I don't think that the brief introduction presents a strong case about why you should spend your time learning the functional paradigm, and specifically Haskell.

In the past, I have shared this short Dr. Dobbs article with my classes: "It's Time to Get Good at Functional Programming" http://drdobbs.com/tools/212201710

Personally, I like Haskell for learning the functional paradigm because it is a pure language, so that you are forced to learn the paradigm to get code running, and you can't slip back into the comfort of your more familiar paradigm (OO, imperative, etc.) Once you learn the new paradigm, you might prefer a multi-paradigm language that allows you to choose the appropriate style for the problem, or sub-problem, at hand. For example, Python supports mixing imperative, object-oriented, and aspects of the functional paradigm.

[Aleksander]

First time I heard about Haskell language in my Software Analysis and Design class. I got interested because functional paradigm was different from imperative, and at the same time its syntax seemed very natural to solving math kind of problems. At least it was my first impression. In addition I did some Internet browsing and found that people used Haskell to write some cool programs and libraries. Then I joined Haskell group in Linkedin just to see where developers use Haskell in professional word. I started to read this book back in May, but then I got busy doing Seven Languages in Seven Weeks problems in my free time, so I’m glad this book was selected for winter break time frame.

[Erik]

I think I will like this book and will learn a lot. It seems well written and the online free version is great (free and very well formatted). The HTML formatted book is easy to read due to the format.

I'm having trouble with the syntax. A lot of the code looks very C-like, but then some code is very not C-like. I'm having trouble jumping back and forth in my mind.