@tomdale react has event delegation, component lifecycles and other structures, etc
-
-
Replying to @jlongster
@jlongster It should be fairly trivial to write your own code to do that on top of virtual-dom, and that way you can customize for your app.3 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster Community is gold, indeed. But why end at "just the view layer"? Seems like a weird place to stop.@tomdale2 replies 0 retweets 1 like -
Replying to @wycats
@wycats@jlongster@tomdale it's a good place to stop, because that's where everybody starts messing things up :)2 replies 0 retweets 5 likes -
Replying to @swannodette
@swannodette in my experience, the only place to go with abstractions is up. Start drawing lines and stop innovating.@jlongster@tomdale2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@swannodette@jlongster@tomdale --the more view and model abstractions are independent, the better. minimize dependencies.1 reply 0 retweets 0 likes -
Replying to @coreload
@coreload@swannodette@jlongster@tomdale what about abstracting the connections between the modules?2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@swannodette@jlongster@tomdale -- exactly, "loosely coupled" and all that.1 reply 0 retweets 0 likes -
Replying to @coreload
@coreload@swannodette@jlongster@tomdale if everyone is using A and B in the same way, seems useful to have a C to abstract that.1 reply 1 retweet 1 like
@coreload @swannodette @jlongster @tomdale even if 20% of people are using things the same way, abstracting it is quite useful.
-
-
Replying to @wycats
@wycats -- I am on board w/that, adding: the dependency mech. shld be usable w/mult. view, model mech. cc/@swannodette@jlongster@tomdale0 replies 0 retweets 0 likesThanks. 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.