elm-ts VS purescript-flame

> By that time, TypeScript had grown to be capable enough (and developer-friendly enough) to balance much of what sold us on Elm originally: a usable type system, good-enough error messages, etc. React had baked in some more useful state management primitives that roughly matched Elm’s “batteries included” state management.

if you like the ideas in elm but don't want to commit to it I'd encourage you to check out elm-ts (https://gcanti.github.io/elm-ts/) It has a little bit more boilerplate than elm (I find elm to be quite verbose already!) but a better experience for individuals and teams overall, I would say. It's a good example of how "TypeScript had grown to be capable enough (and developer-friendly enough) to balance much of what sold us on Elm originally: a usable type system.."

FWIW this post is about PureScript, not Elm. The library is an implementation of the Elm Architecture in PureScript. Elm is a language. The framework that goes along with it is called "The Elm Architecture". The Architecture can be implemented in any language. Here's an implementation in TypeScript: https://github.com/gcanti/elm-ts

There's Purescript with two libraries implementing the Elm architecture, flame and elmish (on React). Purescript only targets JS, but that can be embedded in mobile and desktop apps.

I will also add that Flame is a great way to get Elm Architecture goodness in PureScript.

Flame: A PureScript front-end framework inspired by the Elm architecture\ (30 comments)

Im having a good time using https://flamepurs.org/.

Halogen is definitely the most widely-used library (and someone has already posted links for that), but I just wanted to mention Flame, which has some pretty decent getting started documentation.

Thanks u/suntzusartofarse. There is a upcoming version in the works, with new features https://github.com/easafe/purescript-flame/pull/36