I think we overuse DI in Ember-land atm, there is a balance, will find it.
-
-
-
Replying to @wycats @Runspired and
DI is useful whenever there's "top level state" in modules
2 replies 1 retweet 1 like -
we trickle the pattern down too far though.
1 reply 0 retweets 1 like -
-
Replying to @stefanpenner @wycats and
transforms, validations, transitions.
3 replies 0 retweets 0 likes -
Replying to @Runspired @stefanpenner and
I think auto-wiring is a pretty good pattern, should get more comprehensible 1/
1 reply 0 retweets 0 likes -
Replying to @wycats @Runspired and
with module unification. Afterward, we should revisit. 2/2
2 replies 0 retweets 2 likes -
Replying to @wycats @Runspired and
I think blue prints should be abstracted outside of cli and just use that and throw
3 replies 0 retweets 0 likes -
Replying to @stefanpenner @richardiii and
this is what I mean. Our layering is known to ppl fluent and no one else. Sad!
11:59 PM - 24 Nov 2016
0 replies
0 retweets
1 like
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.