A curated package set and set of tools that let you build Haskell packages so they can run on a variety of platforms. reflex-platform is built on top of the nix package manager.
in the last days I experimented a little with Reflex & Obelisk and I thought, maybe someone could find this feedback useful. Please feel free to ignore it. Otherwise, I'm happy to elaborate and/or create some PRs with suggested changes.
Learning Material
reflex-frp.org is a great starting point
this style of FRP looks incredibly promising for developing large applications.
some things I noticed that could be improved:
Obelisk.Route looks really daunting.The haddock could have some higher-level information e.g. what are the design goals, what is an Encoder,...?
Integration with existing backends: Is it possible to create some kind of wildcard-Route e.g. /api/...? This could be used to implement the backend calls with servant-snap and get the clients for free via servant-reflex.
The tutorial (https://reflex-frp.org/tutorial) does not use the fact (nor mentions) that Dynamic is an Applicative. Instead it uses zipDynWith.
Hi,
in the last days I experimented a little with Reflex & Obelisk and I thought, maybe someone could find this feedback useful. Please feel free to ignore it. Otherwise, I'm happy to elaborate and/or create some PRs with suggested changes.
Learning Material
reflex-frp.org
is a great starting pointObelisk.Route
looks really daunting.The haddock could have some higher-level information e.g. what are the design goals, what is anEncoder
,...?/api/...
? This could be used to implement the backend calls withservant-snap
and get the clients for free viaservant-reflex
.Applicative
. Instead it useszipDynWith.
Contributing