haskellweekly VS mtl-style-example

7. https://haskell.pl-a.net and https://haskellweekly.news

The other suggestion is to look at https://haskellweekly.news/ and specifically at the 'Call for participation' section at the bottom of each issue.

I added "n/a" as a pre-selected answer choice to all single-response questions. (See this commit.) That should allow you to undo accidentally answering a question.

Oh no! I'm very sorry about that. The "X" was definitely meant as a placeholder. I must have forgotten to fill it in. It should be fixed just as soon as this commit is built and deployed: https://github.com/haskellweekly/haskellweekly/commit/5d052eaee9d2cff69f4a6e7c57051e7df139bc80

Re: effects libraries, it's probably worth starting with e.g. https://www.fpcomplete.com/blog/2017/06/readert-design-pattern/ https://www.parsonsmatt.org/2018/03/22/three_layer_haskell_cake.html https://github.com/lexi-lambda/mtl-style-example if you're just getting familiar with the ecosystem. I'll add, anything written by the the people I linked to in this comment is probably worth reading as well.

Personally, it felt to me like, once I really understood monad transformers (https://hackage.haskell.org/package/transformers) and mtl (https://hackage.haskell.org/package/mtl), the reasons they both exist and how they are distinct, how you use them generally and what common patterns are around structuring your app (see e.g. https://github.com/lexi-lambda/mtl-style-example and the 3-layer-cake link someone else provided here for two), a lot of stuff in the ecosystem suddenly became comprehensible and useful to me, in a practical, "real world" way. In fact I'd go so far as to assert that getting comfortable with mtl in particular is the biggest single step you can take to being able to build arbitrarily useful real-world apps that are no longer toys.