DEV Community

Cover image for Haskell for madmen: Hello, monad!

Haskell for madmen: Hello, monad!

DrBearhands on October 16, 2019

Post from my blog. If you're enjoying the series, please consider buying me a coffee. Intro In this chapter we're going to write a hell...
Collapse
 
bootcode profile image
Robin Palotai

Side-discussion: free monads are still monads. And from what I get, free monads are not really that different from programming against a MonadFoo m constraint, in the sense that you can give different implementations at the call site for MonadFoo, while with the free monad you can have different interpreters.

Collapse
 
drbearhands profile image
DrBearhands

You're right, I should have said there are other ways to represent effects than using one single IO monad for everything.

Collapse
 
bootcode profile image
Robin Palotai

No no, sorry, I didn't want to suggest that. I just replied on this paragraph:

I would personally argue that monads are not a good way to represent effects, but they are the current standard for generic functionally pure programming languages. Some other interesting ways of representing effects include uniqueness types and free monads.

I would say the simpler monad tutorials are, the better :)

Thread Thread
 
drbearhands profile image
DrBearhands

I know, emphasis on one monad rather than monads ;-)

Collapse
 
bittnkr profile image
Info Comment hidden by post author - thread only accessible via permalink
bittnkr

Reading this I realized how much I love JavaScript. :D

Collapse
 
lautarolobo profile image
Lautaro Lobo

I'm only here to say that I thought that your profile pic was some kind of draw, or a weird Papagayo... then I opened your profile to see it big and boom, I realized that I'm f**ing blind! ๐Ÿ˜‚

Some comments have been hidden by the post's author - find out more