Converter VS purescript-react-basic

The longer story is that st-material-ui incorporates https://github.com/ScalablyTyped/Converter/pull/487 in order to get much, much cleaner API. You'll probably have seen the fake literal types, some rewriting from type unions to inheritance, things like that.

Given that you want interoperability with js, I'd start by playing with https://scalablytyped.org/, then, play with the scalajs-react demos (https://github.com/ScalablyTyped/ScalaJsReactDemos) and the slinky demos (https://github.com/ScalablyTyped/SlinkyDemos). There are some libraries that scalablytyped doesn't support pretty well but you can leverage https://github.com/nafg/scalajs-facades for those.

ScalaJS is awesome. Really solid and mature project, can totally recommend.

The only thing that can be annoying is when you want to have a typesafe interface and have to write a lot of adapters for javascript libraries.

Fortunately there is even a project that can make use of typescript interfaces for those libraries, so that you can use them from ScalaJS more or less automatically: https://scalablytyped.org/

I'm using it mostly for full-stack web development with ScalaJS (https://www.scala-js.org) in the frontend (https://outwatch.github.io/docs/readme.html) and in the backend with AWS lambdas.

The ecosystem is currently in the process of porting all the libraries to Scala 3. So if you're new to Scala, I'd recommend to start with Scala 2, which is rock-solid and already very powerful.

I never worked with SQLAlchemy. But on the scala database side, popular libraries are Doobie (https://tpolecat.github.io/doobie) and Quill (https://getquill.io). Keep in mind that these are for Scala on the JVM. On the ScalaJS side I'm using the javascript library pg. But I'd like to try if it works well with Prisma soon.

The nice thing about ScalaJS is, that you can use Javascript libraries. And if there are typescript facades, then you can transpile these to Scala and use them in a type safe way (https://scalablytyped.org).

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.