I am recommending CS 1JC3: Introduction to Computational Thinking. Particularly useful is the discussion of state in Thinking Computationally with Elm. It is my hypothesis that the clear exposition on the notion of state and state diagrams will flatten the learning curve relative to the Elm architecture prior to any code implementations being looked at.
Why? Well, I am coming across this whole stuff, not knowing much about the intricacies of building GUIs in the browser enviroment, having a background in mathematics and the Scheme flavoured functional programming approach to building GUIs. So naturally, in reading the Javascript implementation of the Elm Architecture of @nelsonic, I was wanting to relate, compare, and abstract from my prior experience, and what I was missing, was state and state diagrams!
While looking around, gathering context on the problems that React+Redux (what the heck does state container mean anyways?) and Elm are solving, what pains they are relieving developers of, it was only until I watched The Ultimate Introduction to ReactJS on implementing React from scratch, that I had a glimmer of an idea: it is all about state y'all!
another superb link @YvesMuyaBenda you're finding some great content!
(it's super re-assuring to see such an explosion of Elm-focussed learning materials!) 👍
I am recommending CS 1JC3: Introduction to Computational Thinking. Particularly useful is the discussion of state in Thinking Computationally with Elm. It is my hypothesis that the clear exposition on the notion of state and state diagrams will flatten the learning curve relative to the Elm architecture prior to any code implementations being looked at.
Why? Well, I am coming across this whole stuff, not knowing much about the intricacies of building GUIs in the browser enviroment, having a background in mathematics and the Scheme flavoured functional programming approach to building GUIs. So naturally, in reading the Javascript implementation of the Elm Architecture of @nelsonic, I was wanting to relate, compare, and abstract from my prior experience, and what I was missing, was state and state diagrams!
While looking around, gathering context on the problems that React+Redux (what the heck does state container mean anyways?) and Elm are solving, what pains they are relieving developers of, it was only until I watched The Ultimate Introduction to ReactJS on implementing React from scratch, that I had a glimmer of an idea: it is all about state y'all!