learn-you-a-haskell VS wiwinwlh

The LYAH is by far my favorite book for beginners, however, it lacks exercises for you to practice, but you can still move along typing and playing with the examples shown, and it’s free to read online. It’s outdated but most of the code may still be valid with little to no changes.

Learn You a Haskell For Great Good! is also a really good resource:

https://learnyouahaskell.com/

If you've never done functional, Learn You Some Erlang For Great Good was a very fun read, and I'll always love Learn You a Haskell for Great Good for showing me everything imperative languages kinda gloss over magically, as well as why I should never take a job working in Haskell!

you start that way, but don't do http://learnyouahaskell.com really?

Learn You a Haskell for Great Good!

I enjoyed http://learnyouahaskell.com/ which is available in print and digital. Fun and lighthearted while still teaching reasonable depth. YMMV.

Elm is a statically typed language inspired by Haskell. The natural step would be to use Elm on the frontend and Haskell on the backend. And that's what I tried to do. I read with some difficulty the Learn You a Haskell for Great Good! book (available for free here) and learned a lot of cool stuff. But creating a complete backend using Haskell proved to be more than I could chew. So I decided to look for alternatives...

Here y’go!

wiwibwlh

In this respect, The Haskell Guide is not a tutorial, project-based guide or textbook, which aims to give a more complete walk through the language, in a linear fashion, but more like a reference guide that is carefully designed to be accessible and clear. In that respect, it's like a beginner level version of What I Wish I Knew When I Learned Haskell, with more cross-referencing. (By the way, I don't think this is a substitute for more in-depth or didactically rich resources at all; it's trying to address a different problem.)

Many libraries try to stick to Haskell 98. Also whenever someone writes a paper about some new techniques, they always seem to take a lot of pleasure in pointing out when their technique works in Haskell 98.

I like that you can mix and match GHC extensions even in the same project. So one library (or even just one module) might use some crazy and messy extensions, but you can still use it from vanilla Haskell.

http://dev.stephendiehl.com/hask/#language-extensions has a list of extensions and some judgement on them.

For example, I really like TupleSections. They are not strictly necessary for anything, they are purely cosmetic / syntactic sugar. But they also don't cause any mess. https://ghc.gitlab.haskell.org/ghc/doc/users_guide/exts/tupl...

Also: TypedHoles are really neat for developing, and will never show up in your final code. https://ghc.gitlab.haskell.org/ghc/doc/users_guide/exts/type...

Maybe try to implement something using Haskell? For example, try to read through: https://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_Hours to see how the concepts are used in a "real world" setting. Also, https://github.com/sdiehl/wiwinwlh is an underrated resource imo. Anyways, the best way to learn Haskell is to just use it. I'm still learning myself, so I don't have much to say beyond that.