DEV Community

loading...

Discussion on: Haskell for madmen: Hello, monad!

Collapse
drbearhands profile image
DrBearhands Author

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 Author

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

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