After using DOM-centric, declarative, custom elements/components, looking back at code from MVC/Templating libraries will make you nauseous.
-
-
Replying to @csuwildcat
@csuwldcat you still need to keep state, and it's terrible to put that in the dom
3 replies 0 retweets 0 likes -
Replying to @seanmonstar
@seanmonstar a few reasons: 1) no mem, structural, or sync duplication 2) the arg that their TTL is unreliable is a result of improper use.1 reply 0 retweets 0 likes -
Replying to @csuwildcat
@csuwldcat its not a dom-specific problem. Keeping truth in the view is always more complicated
3 replies 0 retweets 0 likes -
Replying to @seanmonstar
@seanmonstar don't get me wrong, I am not saying *all* data/state should exist on DOM objects, only that which pertains to specific nodes.1 reply 0 retweets 0 likes
Replying to @csuwildcat
@csuwldcat I agree, the state of each dom node should be part of the node itself. then the JS app code can keep track of what that should be
10:22 PM - 10 Jul 2012
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.