Re:Backbone Events vs. Ember Bindings: A Benchmark
by jashkenas on Tuesday February 21, 2012 @02:06PM
(#3617631)
Quite, and it's also worth noting that by relying on a "runloop" to defer your renders, you're giving up synchronicity in your data changes -> ui updates when you don't necessarily need to (a very common source of dev bugs in SproutCore 1).
[ Parent
| on HN ]
Re:Backbone Events vs. Ember Bindings: A Benchmark
by bcrescimanno on Tuesday February 21, 2012 @02:20PM
(#3617682)
Not having worked with SproutCore, I honestly can't comment on whether it introduced more bugs. Working with anything async is always going to introduce some complexity; but given the poor DOM performance on low-end devices, deferring rendering is often a very helpful concept.
I'd be interested to hear what type of bugs were common in this scenario; my understanding of the runloop is that after the DOM update (at the end of each loop) the UI should reflect the application state.