purescript-inflist VS purescript-react-basic

If you are curious, there is a GitHub repo with a decently commented code and a live example you can play with 😎.

First of all I had to choose what to use to manage the User Interface. I narrowed down to two modules: Halogen and react-basic-hooks (which is a “wrapper” of the unmaintained react-basic). I decided to go with react-basic-hooks just because I work with React on a daily basis and I wanted to understand its interoperability with PureScript. I will 10/10 try Halogen too in the next future since as far as I can see is the most famous and maintained in the PureScript community.

There's also Purescript, which is sort of a Haskell for frontend. It has type classes, HKTs and so on and also has a very nice FFI. When it comes to UI libraries there is Halogen which I think is very well though out and allows for using tagless final approach. There's also react-basic but I haven't used that one myself.

We use PureScript and React on the frontend and Haskell and Postgres on the backend. On the PureScript side, we use our own purescript-react-basic bindings, and purescript-lumi-components, a UI component library that we built and open-sourced. We get a lot of utility from PureScript’s type system, leveraging the compiler in order to ensure that we don’t get IDs for different entities mixed up, that all API calls are type correct, and that all form data is appropriately validated before it is used. On the Haskell side, we primarily use Servant and Esqueleto. We don’t expect candidates to have experience with all these things. We’d like to find engineers who are interested in learning more about these, and we’ll be happy to teach you.