incredibly proficient teams are constantly tending those fault lines, are acutely aware of their impact, and how to mitigate them
-
-
Replying to @landongn
according to the thesis of the microbros, it would be impossible to rewrite the Ember view layer. Except we did... many times.
1 reply 0 retweets 1 like -
(the Ember view layer is a "giant monolith" with a well-defined API ;) )
1 reply 0 retweets 1 like -
Replying to @wycats
Importance of having a well designed boundary++ Now do the __container__ ;)
1 reply 0 retweets 1 like -
Replying to @landongn
it be coming.https://github.com/glimmerjs/glimmer-di …
2 replies 0 retweets 2 likes -
Replying to @wycats
nice! On that same note, fully opinionated JS stack! (roll them dice, boi)
1 reply 0 retweets 0 likes -
-
-
Replying to @landongn
<3 over time we'll rationalize the whole Ember stack this way. A little at a time.
1 reply 0 retweets 0 likes -
Replying to @wycats
there is so many immediately obvious specifics around networking in particular this would be immensely useful for.
1 reply 0 retweets 0 likes
-
-
Replying to @wycats
DI in general. being able to use generic semantics across tcp/udp/wss/http on both ends, for instance.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.