[giantDinosaur]

Weird that the author says all languages are very similar. Strongly suggest trying something like Elm (although I do not recommend it for any large production use, small areas are fine.) to see how brilliant the experience in another paradigm can be.

[z5h]

I've used Elm at 2 places for large production use, and in a large personal project. It would be my preferred technology by far. I'll add that Elm is actually what converted me from a backend (fullstack at times) engineer to front end. Also realizing that thinking about how people interact with computers and solving those problems well is actually a fun challenge.

[cies]

Me too! Loving Elm. And there are others that break from the pain that frontend otherwise is:

* Purescript

* Kotlin/JS + KVision

* Rust + Yew

* Haskell + Miso

* ReScript + ReReact or TEA

* F# + Elmish

Hell even TypeScript + TEA would be a great alternative: https://github.com/typescript-tea/core

A hot topic still is CSS that non of these solve, so an additional lib is needed there. TailwindCSS has been my go to lately, and I really start to get the hang of it (great docs also!!).

[giantDinosaur]

Not necessarily solved, and I assume you know about it, but for anyone reading this, elm-ui is definitely worth checking out for at least an exploration of an alternative to CSS.

For a talk about this: https://www.youtube.com/watch?v=Ie-gqwSHQr0

[ronanyeah]

I would personally recommend Elm for production use after 3 years of development with it.

I regularly engage in refactoring efforts that would be prohibitively time consuming in React, which I also have production experience with.

[carapace]

Yeah, just use Elm.