purescript-flame VS purescript-concur-react

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

Before 2012, all of my websites were made using HTML, CSS and a sprinkling of JS. Then, I went all-in on AngularJS, followed by React. I started using Typescript and then PureScript and learned more frameworks like Halogen and Concur. I even wrote my own UI framework called purescript-deku.

I was wondering that myself. Here's an Ajax example: https://github.com/purescript-concur/purescript-concur-react...

It could use some type signatures, but it makes sense.

As for managing state, my understanding of the Elm Architecture is that there is one "global" state data structure, and various parts of it are handed down from parent to child. So my question would be the opposite of yours: what if I want local state? Is that possible? There are situations where some toggle being on or off isn't very important and keeping track of it in a global data structure is burdensome

And here is an example of a fully editable tree in a handful of lines of code using signals - https://github.com/purescript-concur/purescript-concur-react/blob/master/examples/src/Test/EditHeadingsSignals.purs.

The author of the article might be interested in seeing the counter example in purescript-concur