The Effectful effect system has a website: haskell-effectful.github.io

#1

One of the main barriers to entry when adopting an effect system is that you have a whole ecosystem to discover an adopt. In order to aid discovery, and provide a place for the maintainers and contributors to provide a curated list of bindings, Effectful now has a website to aid adopters pick bindings for various tasks (network, data storage, logging…).

The website has a blog section that is intended to long-form write-ups where design choices and deep dives will be presented. Since Effectful is intended as a foundation for your applications, it’s important to be extremely clear about how it works.

Check it out: https://haskell-effectful.github.io
Please submit your bindings at GitHub - haskell-effectful/haskell-effectful.github.io: GitHub Pages for effectful.

image
image512×512 32.8 KB

32 Likes
#2

And I want to publicly acknowledge how delightful it is to work with @arybczak in the Effectful ecosystem. His focus on usability, and being a welcoming maintainer, has been crucial in making me feel like I want to be involved.

11 Likes
#3

This is really nice!

#4

Effectful is so lovely to work with. This is a great idea, and I can see how it will help grow the ecosystem.

I just submitted a PR to add hyperbole to the web-development section. Thanks for all your hard work!

3 Likes
#5

Thanks @Kleidukos, this is a great start. Personally I’m really looking forward to the deep dives and design writeups, since I’ve been looking (without success) for something like this.

Quick question - what is the development status of servant-effectful? I see that there hasn’t been any code changes for about 2 years, nor has it been uploaded to Hackage. Is there any intention to do so?

1 Like
#6

Good question, it’s just that two years ago @tristanC landed a PR that was enough for it to be usable in production without major drawbacks. I’m actually about to change some stuff in the API to enable the passing of middlewares, but mostly servant-effectful does not get in the way of day-to-day development of Servant applications, hence why it did not require too much work these past two years.