4 ms·
electricity and other modern day conveniences are also not necessary to stay alive, but it sure makes it a lot more comfortable.
by chii 14y ago
electricity and other modern day conveniences are also not necessary to stay alive, but it sure makes it a lot more comfortable.
- lmm 14y agoDo you have an example of something that can be more comfortably expressed with a monad, even in a language with imperative constructs? To me monads have always seemed like a crutch for a deficient language. (A lisp advocate once told me tail recursion was great because it let you write an event loop without getting a stack overflow. The example code they gave would have been much clearer as a "while" loop, but I guess lisp doesn't have those. It seems like the same thing to me)
- olavk 14y agoA better reason: Tail recursion lets you implement "while" if you miss it.
- lmm 14y agoThat explains why I want tail recursion in lisp, a language that doesn't have "while". But it doesn't explain why I would ever want or need tail recursion in python, which already has while. In the same way, I can see why I want monads in Haskell. But why would I ever want or need monads in a language that has first-class imperative constructs?
- olavk 14y agoAgreed about tail recursion in Python, promoting recursion as an alternative to loops is contrary to the sprit of Python and "one obvious way to do it". Monads vs imperative languages is a bit different though, since Haskell-style monads are more than just a way of allowing an imperative style. For example many other features like list comprehensions and parsing is also based on monads in Haskell. However the real value of Haskell-style monads is that it is clear when you don't use them. So it is explicit in the type system which functions have side effects and which don't.
- lmm 14y ago>Monads vs imperative languages is a bit different though, since Haskell-style monads are more than just a way of allowing an imperative style. For example many other features like list comprehensions and parsing is also based on monads in Haskell. So maybe monads are useful for implementing language internals. But if we assume my language has list comprehensions and a parser (however they're implemented internally), what would I as a user of the language want monads for? I keep hearing that monads are great, but every code example I've seen using them seems like something that I could do more easily in python, without a monad. So I'd really like to see any examples of code that you would want to write using monads, even in a language that has imperative constructs.
- talaketu 14y agoCheck some of the pyparsing examples.
- jerf 14y ago"Do you have an example of something that can be more comfortably expressed with a monad, even in a language with imperative constructs?" STM. And it may not be immediately obvious that it does need to be a monad, if you don't deeply understand how it is being used. There's more to it than meets the eye at first.
- gliese1337 14y ago"STM" to me means "Scanning Tunneling Microscope", so I was a bit confused until I googled and realized "Ah! Software Transactional Memory!" And you're right, it's not immediately obvious that it needs to be a monad. Could you elaborate?
- Locke1689 14y agohttp://research.microsoft.com/en-us/um/people/simonpj/papers/stm/beautiful.pdf http://research.microsoft.com/en-us/um/people/simonpj/papers...
- jerf 14y agoI'm going to run on the theory you don't know Haskell. In this case, it's like someone who doesn't know OO at all asking why on Earth they'd want the Factory pattern. It isn't that I can't explain it per se, but no satisfying answer can be fit into an HN post. So I didn't try. To forestall the "copout" accusation: Basically, being a monadic value means you get the full range of monadic programming constructs available to you while still being isolated by the type system, so you get isolation while still being able to do real work, and the STM system takes extensive advantage of the fact that the do syntax actually desugars into a long series of closures, which means it can do things like retry and choice and stuff in a natural, safe way. But I am well aware that doesn't sound very impressive in isolation, because there's still a great deal of important nuance lost in that description, in much the same way that a similarly-detailed description of the factory pattern sounds generally unimpressive. ("What, it lets me either construct one thing or the other? Big whoop, here's how I do it in my procedural language, basically by just doing it. What's the big deal? Why does it make such a big fuss over something so simple?" Which is a good question, if asked honestly, but a terrible argument, which is how it would usually be meant.)