You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+60-15Lines changed: 60 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ When we encounter this type of "_what is the **right way**_?"
53
53
question <br />
54
54
we always follow [***Occam's Razor***](https://en.wikipedia.org/wiki/Occam%27s_razor) and _ask_:
55
55
what is the ***simplest way***? <br />
56
-
In the case of web application organization,
56
+
In the case of web application organization,
57
57
the ***answer*** is:
58
58
the "**Elm _Architecture_**".
59
59
@@ -63,13 +63,13 @@ When compared to _other_ ways of organizing your code,
63
63
+ Easier to _understand_ what is going on in more advanced apps because there is no complex logic,
64
64
only one basic principal
65
65
and the "_flow_" is _always_ the same.
66
-
+***Uni-directional data-flow*** means "state"
66
+
+***Uni-directional data-flow*** means "state"
67
67
of the app is always _predictable_;
68
68
given a specific starting "state" and sequence of update actions
69
69
the output/end state will _always_ be the same. This makes testing/testability
70
70
very easy!
71
71
+ There's **no** "***middle man***" to complicate things
72
-
(_the way there is in other application architectures
72
+
(_the way there is in other application architectures
73
73
such as
74
74
[Model-view-Presenter](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter) or "Model-View-ViewModel" (MVVM) which is "overkill" for most apps_.)
75
75
@@ -85,12 +85,12 @@ their code/app in a _sane_, predictable and testable way.
0 commit comments