elm-ts VS Cycle.js

> 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

Seems like you might be interested in this

Cycle

This is the standard way of going about things in Mithril and Cycle. Elm as well doesn't use an XML knockoff for view code- and as a fun fact, the original version of React didn't either.

For example, an FRP framework (created by the same author who later wrote the callbag spec): https://cycle.js.org/

TypeScript is relatively mainstream at this point, and I think that's good news. If you want to crank the type-safety and pure FP dials on it to 11, you certainly can do that. I have a project that I've based largely on this post, including the "hardcore" section. However, instead of Redux and otherwise plain React, I've chosen to use Cycle.js and the lessons from this post to use React in a very purely Functional Reactive Programming Way.

This post links to a PureScript project that is probably the easiest PS framework around.

ReScript + rescript-react is a good alternative. Less safe, waaaay more verbose; but backed by Facebook.

This is quite cute (in TypeScript though): https://github.com/cyclejs/cyclejs

And Yew is super cool, it goes the WASM route (in Rust): https://github.com/yewstack/yew

From now on I was on what I would call a typical open source trajectory. I used the Cycle.js framework to rewrite my frontend and in that process I hit some walls. I eventually figured that the error was on my side and that I was just missing some information to avoid the error. To spare others the hours of debugging I started to contribute small patches to the documentation. At the same time I also found some missing features that I voiced in GitHub issues.