notes/2021-03-14--13-00-04Z--the_service_pattern.org
This commit is contained in:
parent
748b3f42ed
commit
4cc160cbd8
1 changed files with 3 additions and 3 deletions
|
@ -119,7 +119,7 @@ dimensions without worse evaluation in some dimension.
|
|||
Typically, a code architecture is preferable to no code architecture as
|
||||
soon as your code become big enough and you need to not work alone.
|
||||
|
||||
For example I would argue that the Purescript Halogen architecture is
|
||||
For example Purescript Halogen architecture is
|
||||
probably strictly superior to the Elm Architecture.
|
||||
Because it contains Elm Architecture but also contains a shortcut mechanism
|
||||
which is entirely enforced via static types..
|
||||
|
@ -157,9 +157,9 @@ your application need to launch and you could potentially only enable part
|
|||
of them you just need to take care that every enabled component also have
|
||||
every of its sub-component enabled.
|
||||
|
||||
This look easy, but I dare you to achive this in Haskell.
|
||||
This look easy, but I dare you to achieve this in Haskell.
|
||||
Because it relies a lot on runtime properties.
|
||||
This is frustrating as we feel we could put a lot of static informations.
|
||||
This is frustrating as we feel we could put a lot of static information.
|
||||
|
||||
What does this buy us?
|
||||
|
||||
|
|
Loading…
Reference in a new issue