notes/2021-03-14--13-00-04Z--the_service_pattern.org

This commit is contained in:
Yann Esposito (Yogsototh) 2021-10-31 16:10:18 +01:00
parent 748b3f42ed
commit 4cc160cbd8
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646

View file

@ -119,7 +119,7 @@ dimensions without worse evaluation in some dimension.
Typically, a code architecture is preferable to no code architecture as 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. 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. probably strictly superior to the Elm Architecture.
Because it contains Elm Architecture but also contains a shortcut mechanism Because it contains Elm Architecture but also contains a shortcut mechanism
which is entirely enforced via static types.. 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 of them you just need to take care that every enabled component also have
every of its sub-component enabled. 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. 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? What does this buy us?