Data-binding Revolutions with Object.observe()

object observe

A revolution is coming. There’s a new addition to JavaScript that’s going to change everything you think you know about data-binding. It’s also going to change how many of your MVC libraries approach observing models for edits and updates. Are you ready for some sweet performance boosts to apps that care about property observation?

Okay. Okay. Without further delay, I’m happy to announce Object.observe() is landing in Chrome 36 beta. [WOOOO. THE CROWD GOES WILD].

Object.observe(), part of a future ECMAScript standard, is a method for asynchronously observing changes to JavaScript objects…without the need for a separate library. It allows an observer to receive a time-ordered sequence of change records which describe the set of changes which took place to a set of observed objects.

To read more, see my complete deep-dive on O.o() over on HTML5Rocks.



Gulp And Grunt Tasks For Performance Optimization


Delays in performance have the potential to impact user engagement, experience and revenue. Thankfully, Google’s ‘Make The Web Faster’ team recommend a set of best-practice rules for keeping your pages lean, fast and smooth. These include minifying resources like CSS and JavaScript, optimizing images, inlining and removing unused styles and so on.

If you have complete control over your server, an excellent PageSpeed Module for Apache and Nginx exists with filters for many of these tasks. If not however, or you feel the module isn’t quite for you, a number of build-tasks exist for tools you’re probably already using to fill in the gaps with more granular control.

For a complete list of Gulp and Grunt tasks the Yeoman team recommend for your build process, see my complete write-up on the Yeoman blog.