Flame: A PureScript front-end framework inspired by the Elm architecture

Purescript-Concur is simpler, and allows you to use elm-architecture as well, but also allows you to use your existing functional programming toolkit to the fullest. It also has react bindings - <a href="https:&#x2F;&#x2F;github.com&#x2F;purescript-concur&#x2F;purescript-concur-react" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;purescript-concur&#x2F;purescript-concur-react</a>.<p>Here&#x27;s what a counter example looks like -<p><pre><code> counter count = do button [onClick] [text (show count)] counter (count + 1) </code></pre> Check out a comparison with elm-architecture at <a href="https:&#x2F;&#x2F;ajnsit.github.io&#x2F;concur-documentation&#x2F;ch03-01-replicating-elm-architecture.html" rel="nofollow">https:&#x2F;&#x2F;ajnsit.github.io&#x2F;concur-documentation&#x2F;ch03-01-replic...</a>.

Elm handicaps my attempts of &quot;making impossible states impossible&quot; because:<p>- I can&#x27;t have Sets of arbitrary Types they must be `comparable`. I cannot create a custom comparable type.<p>- Records, Bool and custom Union Types are not `comparable`<p>- Bool and Simple Union Types could have been comparable if their comparison worked like they were Enumerated Types. Elm does not have Enumerated types.<p>Basically <a href="https:&#x2F;&#x2F;github.com&#x2F;elm&#x2F;compiler&#x2F;issues&#x2F;1008" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;elm&#x2F;compiler&#x2F;issues&#x2F;1008</a> made me look for better alternatives.

Impressive metrics <a href="https:&#x2F;&#x2F;flame.asafe.dev&#x2F;benchmarks" rel="nofollow">https:&#x2F;&#x2F;flame.asafe.dev&#x2F;benchmarks</a>

I&#x27;m really happy to see more PureScript support! I recently built a playground for purs in the browser: <a href="https:&#x2F;&#x2F;app.qvault.io&#x2F;playground&#x2F;purs" rel="nofollow">https:&#x2F;&#x2F;app.qvault.io&#x2F;playground&#x2F;purs</a>

Nice, looks very clean.<p>As in Elm, I’ve never fully understood why the events emit a value of some message type that gets interpreted into a function from ‘state -&gt; state’ instead of handling with a state transformation directly.<p>Feels like boilerplate to me. I can see situations where this approach is useful, but should it be the default?<p>I guess you can always change your message type to ‘a -&gt; a’ and interpret with ‘id’ if you want to.

Amazed to see PureScript is still around, I guess.<p>It was everywhere on conferences like 5 years ago.

Misread that as &quot;PostScript&quot; and was confused but curious.