The Elm Architecture[1] makes it easy to reason about code. You render the current state. You create a new state by applying a message to the current state.

1. https://guide.elm-lang.org/architecture/

You really need to use it to see the light. It's like reading about programming and actually programming. You don't understand programming until you actually program.

You won't understand why elm is simple until you actually use elm to the point of internal understanding. I think doing this is much harder nowadays given that most people would likely use an LLM to do most of the coding.