Data Binding Internals and Mobile Performance about discussion

[yyx990803]

Vue.js' data binding implementation actually falls in the KVO camp (similar to Ember), but with auto dependency tracking (similar to Knockout). As shown in Pete's talk, KVO have really fast warm updates because under the hood it's just callbacks, and you pay slightly more for the initial render because of the need to setup the data observation and dependency graph.

I don't really see fundamental memory issues for KVO on mobile from the talk, because it simply doesn't make sense to render 10k items at the same time on a mobile device (and in that worst case scenario it uses 30mb of memory). A sanely-designed mobile app probably has less then a tenth of that many items at any point, left alone in the viewport. As seen in the talk at 1k items / 10k DOM nodes, the memory usage difference is 14.6mb vs 13mb, which is not significant at all. I'd argue that worrying about memory issues for KVO on mobile is like worrying about >16ms render time for React, both are rare edge cases and can be avoided when done right.

[pltod]

Thanks for the classification of Vue.js in respect to data binding approach! It was interesting to read your comments on the video as well...

[ravindranathakila]

FYI this page comes up #4 for Googling "vuejs mobile" 👍