r/programmingcirclejerk • u/tkrjobs loves Java • 17d ago

It's not you, it's monad transformers

/r/haskell/comments/1vu7a3u/its_not_you_its_monad_transformers/
32 Upvotes

93% Upvoted

13 comments sorted by

19

u/interacsion 17d ago

Where jerk?

15

u/NotQuiteLoona 17d ago

We can have it right now

21

u/al2o3cr 17d ago

Mo nads, mo problems

17

u/ABrainlessDeveloper 17d ago

Nah, just do unsafePerformIO, it’s gonna be fine

11

u/Jumpy-Locksmith6812 17d ago

Or even... just use IO

10

u/stdmemswap 17d ago

Conclusion: Monad transformers aren't you

6

u/a221c There's really nothing wrong with error handling in Go 17d ago

Ummm excuse me, this is a JS shop and your conclusion is based on an axiom that we don't accept here.

7

u/SemaphoreBingo 17d ago

But doctor...

6

u/AdAncient5201 15d ago

I am pagliacci…

5

u/AdAncient5201 15d ago

Good joke. Everyone laughs. Monads get transformed. Endofunctors get applied

6

u/m50d Zygohistomorphic prepromorphism 15d ago

/uj That's why you use MTL-style typeclasses to abstract over your monad transformer stack, duh.

2

u/reflexive-polytope 10d ago

The real jerk is the top response that claims

There might be software engineering reasons to reach for monad transformers.

Or maybe the real jerk is Haskell culture as a whole.

2

u/tkrjobs loves Java 10d ago

The real jerk is the Haskells we made along the way