elm-architecture-tutorial VS flux

I'm learning Haskell right now, pure functional language, but if anyone is interested, Elm is based on Haskell and much easier to learn. Elm is a web development language that compiles to JS. https://guide.elm-lang.org/

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

And if you want to stay in the UI realm, Elm is a good introduction into functional programming.

If you want to get better at data structures you should strongly consider learning a functional language. A huge part of functional programming is manipulating data structures. The language Elm is a great place to start for you since it's frontend specific. For example, check out the doc page for the Dict data type and see if that kind of stuff is what you're looking for.

https://guide.elm-lang.org/ for a high level guide, and an unstyled button example https://elm-lang.org/examples/buttons.

I hope this tiny guide was helpful, and that you learned something new today. If you want to learn more about Elm, you should check out the official guide or say hello in the Elm Slack #beginners channel

https://guide.elm-lang.org/ is always a solid example for me

After going through the whole Introductory Guide to the Elm Language and reading the Elm in Action book, I already felt quite comfortable developing webapps in this paradigm. I liked Elm so much that I started a project to teach programming to beginners using this language and made the first classes available on the website elm.dev.br (in Brazilian Portuguese).

So Flux architecture with the concept of Stores, Dispatchers, and Actions came about (from React team), and then Redux (a simplified version of Flux - for juniors by a junior).

Flux Homepage

Then came Flux.

So the basic fundamental of state management is to cache recurring data which is to be passed along a lot of component hierarchy. Input/Props drilling is one the issue where state management methodology like flux comes to resort. A central global store that will act as hydration of data to our components and probably act as single source to truth for many entities in your application.

https://github.com/gaearon/flux-react-router-examplehttp://ianobermiller.com/blog/2014/09/15/react-and-flux-interview/https://github.com/facebook/flux

Throughout the examples and explanations of Flux architecture -- Facebook's counterpart to React -- action type names are referenced as enum constants rather than strings. (See examples at http://facebook.github.io/flux/) I am just looking for an articulation of why this is the preferred method.

Flux. Redux's claim to fame was capturing Flux's functionality in a simpler API.

I'm reading about Flux but the example Todo app is too simplistic for me to understand some key points.

You should look into the Flux architecture pattern. It provides a clear structure for managing application state, and there are libraries out there that implement the pattern that you can use if you don't want to roll your own state management solution.