3 ms·
> monad, that structure is actually uninteresting here because it is too powerful I am worried these days that people are avoiding talking about monads not bec
by klodolph 14y ago
> monad, that structure is actually uninteresting here because it is too powerful
I am worried these days that people are avoiding talking about monads not because they are not useful, but because places like HN were saturated with talk about monads a few years back. I remember seeing several blog posts explaining monads as some kind of revelation: like they were overloaded semicolons, or monads were burritos, etc. So let's not try to let the popularity of monads interfere with our respect for their powerful and simple structure.
It's kind of like saying that sets are uninteresting in mathematics because they are too general. The Haskell community still does talk a lot about monads, and they are interesting and useful. Monads are what let us describe things like the difference between IO, ST, and STM. Monads give us generalizations of list comprehensions and give us ways to simulate nondeterministic execution.
In short, monads are still king; but the Haskell community is much more aware of the diversity of useful algebraic structures than it was.
- jerf 14y ago"uninteresting here", which is to say, in this context. Yes, they are still fantastically useful, despite having a terrible PR department over the past decade, but in terms of extracting maximal usefulness from things like "this operator is associative" they aren't very interesting, because they are too powerful, or, equivalently, make too few guarantees.
- klodolph 14y agoI still have to disagree. Covariance turns generality into specificity, so any argument that states "monads are uninteresting here because they are very general" should be paired with, "except in the dual case in which they are very interesting because they are very specific."