haskell-handbook VS Cabal

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 .

Also, there's already a cabal RFC to support toml: https://github.com/haskell/cabal/issues/7548

Cabal has a lot of dark corners once you stray from the happy path. Just checked and I'm currently subscribed to 37 threads on the issue tracker, and I'm not a maintainer. A lot of these are related to lesser-used features like cabal scripts, environment files and doctests (though I think all of these things would used more if they were more reliable), but there's also plenty of stupid stuff like: - https://github.com/haskell/cabal/issues/3313 - https://github.com/haskell/cabal/issues/8527 - https://github.com/haskell/cabal/issues/8391 - https://github.com/haskell/cabal/issues/7789 - https://github.com/haskell/cabal/issues/6888 - https://github.com/haskell/cabal/issues/6999 - https://github.com/haskell/cabal/issues/5271

Given that Mike Pilgrim (the Stack maintainer) is on Windows, and Cabal has issues on Windows, I think it might be easier to get Windows specific fixes merged in Stack.

The error message is not too helpful. This is the target of a long-standing ticket: https://github.com/haskell/cabal/issues/7993 Your help would be very welcome.

By the way, there are some open issues for the command to add a package in Cabal.

That's interesting. Could you could open a an issue about this? https://github.com/haskell/cabal/issues

I created this issue a few months ago: https://github.com/haskell/cabal/issues/8270

Reported this as a bug in cabal.

We definitely plan to have benchmarks once we start working on performance. We haven't started yet because there were more urgent tasks. For example: ensuring that the testsuite runs on CI with the JS backend (should be completed this week or the next), ensuring that the toolchain works properly (we're writing a tutorial and we've found new bugs, e.g. yesterday I've fixed the support for js-sources in Cabal https://github.com/haskell/cabal/pull/8636), adding TH support...