Regarding TS & Flow: I’d choose a pure language with immutable data over an impure one with static types. State is the cause of complexity.
-
-
Replying to @max_hoffmann
this is tricky - FP is a good exercise to reduce reliance on state, but modelling the real world requires state, thoughts?
1 reply 0 retweets 0 likes -
Replying to @petr_tik
Elm’s architecture of pushing state to the system’s boundaries and stepping the pure app forward in time with Msgs works well.
1 reply 0 retweets 0 likes -
Replying to @max_hoffmann @petr_tik
A first step is separating essential from accidental state and designing a system that separates those.
1 reply 0 retweets 0 likes
Replying to @max_hoffmann
that's what people mean with 'fp makes you a better programmer', with FP habits you will write clean, decoupled OOP
3:05 AM - 26 Aug 2016
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.