Sep 2014
15 Mon
16 Tue
17 Wed 09:30 AM – 06:15 PM IST
18 Thu 08:30 AM – 06:00 PM IST
19 Fri 08:45 AM – 05:30 PM IST
20 Sat 08:45 AM – 05:15 PM IST
21 Sun
Bhargava Srinarasi
@srinarasi
Submitted Jun 30, 2014
We have been using MV* frameworks to get notifications when a javascript object is updated in our webapp. But they came with either of the two disadvantages.
We now have a native JS way to achieve this in a way that lets us have the best of both worlds.
When we are building a Webapp, we almost always need a mechanism to detect changes to objects that we care about so that we can process the changes. Until now, we had to depend on some frameworks which were doing some form of dirtychecking to implement this functionality. Now, we have an efficient, native way to do it.
In the session, we’ll talk a bit about how we use frameworks like Backbone, Ember and Angular to achieve data binding. We’ll talk about the disadvantages with each of them. We’ll then talk about the new Object.observe and it’s advantages. Finally we’ll go through a few examples and benchmarks.
Experience of using any MV* Framework
A member of Adobe Dreamweaver Development team, Bhargava has been working at Adobe for more than 6 years. His interests include web development, data analysis, data visualization and building tools to help others with the same. He has contributed to open source IDEs like Brackets. He likes talking about himself in third person.
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}