@therealadam "Boundary" doesn't really capture how hard it is to properly create them, which is why frameworks boost productivity.
-
-
Replying to @wycats
@therealadam Boundaries have to work hard to avoid leaking concerns by accident (especially in dynlangs), and ad-hoc boundaries leak hard2 replies 0 retweets 0 likes -
Replying to @wycats
@therealadam "don't call me, I'll call you" seems like 6 of one, half-dozen of another, but "I'll call you" can offer more guarantees.1 reply 0 retweets 0 likes -
Replying to @wycats
@therealadam "the didInsertElement hook" (or componentDidMount in React) is guaranteed to be called at the right time, which isolates DOM1 reply 0 retweets 0 likes -
Replying to @therealadam
@therealadam one really common boundary people forget about is "startup time". Many people try to ignore it and just use global state.1 reply 0 retweets 0 likes -
-
Replying to @therealadam
@therealadam yes, but services people are doing services because they hate the idea of frameworks, so it's a poor cultural fit.2 replies 0 retweets 0 likes
@therealadam in some circles, it's axiomatic that frameworks do more harm than good.
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.