haskell-handbook VS strong-path

All together that was a thoughtful and fair write up, thanks for that! I think you are spot on regarding monad transformers. Testing story is very good, the only part that I found harder then I would like it to be is testing IO code - there are some solutions that help but still, it is a bit surprisingly complex. And Template Haskell - it is not as hard as it sounds! Can be quite powerful without super deep knowledge. Btw here is short "cheat sheet" for Template Haskell that I wrote as notes for myself and others in the company: https://github.com/wasp-lang/haskell-handbook/blob/master/template-haskell.md .

haskell-handbook

I am trying to do something similar with https://github.com/wasp-lang/haskell-handbook, but much less ambitious - it is mostly there for me and my colleagues, not as a general guide, and is for intermediate level, not beginners, also has no order, just topics. But what I do is create issues with quick drafts and then fill them in when I have time and others can also add to it.

Wrote some popular tutorials on Haskell concepts, like https://wasp-lang.dev/blog/2021/09/01/haskell-forall-tutorial, and also are maintaining haskell handbook (still in infancy): https://github.com/wasp-lang/haskell-handbook .

I actually wrote a short text about how functions behave as Functor, Applicative or Monad: https://github.com/wasp-lang/haskell-handbook/blob/master/function-as-functor-applicative-monad.md .

Recently I realized I have no idea how should I define version bounds for my library and I got pretty confused before I finally figured out the reasoning behind it (thanks to r/haskell and Adam Bergmark from Stackage), so I thought I would capture that reasoning in a short article: https://github.com/wasp-lang/haskell-handbook/blob/master/dependencies-version-bounds.md .

As a result I decided to write a small article that gives overview of Cabal and Stack are and also compares them, based on what I learned: https://github.com/wasp-lang/haskell-handbook/blob/master/cabal-and-stack.md .

To support this with an example, executable with pinned dependencies would be https://github.com/wasp-lang/wasp/blob/master/waspc/package.yaml , while a library with loose dependencies would be https://github.com/wasp-lang/strong-path/blob/master/package.yaml .

I wrote a strong-path package, which I published on Hackage. I am using Stack to build it: I have stack.yaml and package.yaml as sources of truth, while strong-path.cabal is generated by Stack but I also commit it into vcs.