I'm going to grab the version. But I'll bet it's not ember2 which I guess you're referring to.
-
-
Replying to @CiaranReen
modern ember began around 1.11/1.12 but most too until 2.x to adopt using those patterns.
1 reply 0 retweets 0 likes -
Replying to @Runspired
I remember a talk from
@wycats where he was talking about the evolution of ember. Indeed it's come far.1 reply 0 retweets 1 like -
Replying to @CiaranReen @Runspired
even taken some cues from the flux ideology if I remember correctly
1 reply 0 retweets 1 like -
Replying to @CiaranReen
two-way binding is cool and still has it's place, but I think we all recognize going all in on it was a big mistake.
1 reply 0 retweets 0 likes -
Replying to @Runspired @CiaranReen
the big open question has to do with form fields.
@chancancode long ago convinced me they require more thinking.1 reply 0 retweets 1 like -
I think microstates and changesets with explicit model change flow is generally the right direction
1 reply 0 retweets 0 likes -
-
Replying to @Runspired @CiaranReen
's point has to do with form fields managing internal state, but 140 chars isn't enough. Let's catch up.
2 replies 0 retweets 2 likes -
Replying to @wycats @Runspired and
Seems to me that the problem is HTML form fields are stateful... kinda.
1 reply 0 retweets 0 likes
Nah the problem is some parts of state (cursor, selection) aren't represented by upstream data
-
-
Replying to @wycats @Runspired and
hmm, is the end goal to abstract the browser away from the browser?
0 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.