Counterpoint: ReactJS solves a lot of engineers' problems in a clean and elegant way. Even if it goes away, the ideas behind it will continue to be good ones.

There's nothing wrong with Haskell, but I think that a lot of people mythologize it because it's not used by many people and has an air of academia. A lot of people do the opposite to ReactJS because it's a popular framework that a lot of people use. It has no mythos. Of course, mythos is orthogonal to actually having practical, useful ideas.

The architecture underpinning ReactJS offers some generally useful abstractions (that have appeared previously in other forms). The difficulties arise when the implementation of abstractions are viewed as a magical property of some programming languages rather than others. It doesn't matter whether it's 'object orientated' or 'functional' or 'one way data flow'.

I've literally just started doing this, starting with category theory. Here's what I've been watching:

- https://youtu.be/I8LbkfSSR58?list=PLbgaMIhjbmEnaH_LTkxLI7FMa...

- https://www.infoq.com/presentations/category-theory-proposit...

I'm very, very, very open to suggestions... especially if they're presented from the ground up, and in lots of detail. I'm also quite open to material that can be read rather than watched.

I have these same exact goals myself. Happy learning!

Have you tried using ReactJS?