journal/2021-03-14--13-00-04Z--service_pattern.org
This commit is contained in:
parent
e484e89d09
commit
40027e1033
1 changed files with 5 additions and 1 deletions
|
@ -52,4 +52,8 @@ But with FRP the author clearly though it was a good-enough design pattern.
|
|||
But the design space was a bit too big.
|
||||
So it was difficult to take the right decision.
|
||||
So a natural meta-pattern appeared.
|
||||
It is [[https://guide.elm-lang.org/architecture/][/elm architecture/]]
|
||||
It is [[https://guide.elm-lang.org/architecture/][/Elm Architecture/]].
|
||||
So while Elm imposed so structure of your program using static types to
|
||||
prevent common coding mistakes and enforce a specific code structure.
|
||||
Elm did not constrain the file organisation, the number of buffers to
|
||||
send/receive events, the way they should talk/listen between each other.
|
||||
|
|
Loading…
Reference in a new issue