Interactive programs without callbacks or side-effects. Functional Reactive Programming (FRP) uses composable events and time-varying values to describe interactive systems as pure functions. Just like other pure functional code, functional reactive code is easier to get right on the first try, maintain, and reuse.
Hello. I'm trying to setup a skeleton project with reflex-platform, servant-server, servant-reflex, nixops, ghcid and a simple makefile providing ob-* like commands. Everything works fine except I struggled trying to do client-side routing so I'd like to ask three questions.
1) It seems that Obelisk is the only recomended way do client side routing now? https://github.com/reflex-frp/reflex-dom-contrib/issues/55#issuecomment-429356956.
2) Even if client-side routing can be solved (without Obelisk). There are other good reasons to use Obelisk, for someone already using servant, ghcid, make and nixops in all other non-reflex projects?
3) If possible, where can I find a working example of servant-snap with a recent version of Obelisk?
Hello. I'm trying to setup a skeleton project with reflex-platform, servant-server, servant-reflex, nixops, ghcid and a simple makefile providing ob-* like commands. Everything works fine except I struggled trying to do client-side routing so I'd like to ask three questions.
1) It seems that Obelisk is the only recomended way do client side routing now? https://github.com/reflex-frp/reflex-dom-contrib/issues/55#issuecomment-429356956. 2) Even if client-side routing can be solved (without Obelisk). There are other good reasons to use Obelisk, for someone already using servant, ghcid, make and nixops in all other non-reflex projects? 3) If possible, where can I find a working example of servant-snap with a recent version of Obelisk?
Thanks a lot.