3 ms·
It looks very similar to how yesod (http://www.yesodweb.com/ http://www.yesodweb.com/, http://www.yesodweb.com/book/basics http://www.yesodweb.com/book/basics)
by PeterisP 13y ago
It looks very similar to how yesod (http://www.yesodweb.com/ http://www.yesodweb.com/, http://www.yesodweb.com/book/basics http://www.yesodweb.com/book/basics) routes/handlers are implemented - is that what you mean?
- pka 13y agoNot quite - iirc Yesod still runs in some kind of IO monad, i.e. it is stateful. In contrast signal functions are declarative (pure).
- PeterisP 13y agoInteracting with a DB or reading a html file from disk is in essence non-pure.
- pka 13y ago[1] is a good simple explanation of what FRP is about. A DB interaction for example can be viewed as a pure function from a signal of Requests to a signal of Records. Same with files (Signal Path -> Signal FileContents), etc. [1] http://elm-lang.org/learn/What-is-FRP.elm http://elm-lang.org/learn/What-is-FRP.elm
- colanderman 13y agoThe IO monad is also declarative. But, just like FRP signal functions, functions in it can be used to describe stateful systems.
- tel 13y agoDespite not having gotten too deep into Yesod, I'd be surprised if they're similar. FRP is solving a very different problem than route handling.