One of the best ways to prevent page bloat is to treat everything as a resource that doesn’t need to be on the page until the user has to interact with it. The technique is called lazy-loading, and can be performed on almost any asset. It’s especially good for responsive websites, when the same content needs to be loaded across multiple devices, while still loading as quickly as possible. Let’s take a look at a few ways to make this possible.
Dennis Gaebel previously discussed preparing for ES6, but in this post he take things one step further and examines an actual project using the tools he discussed in that article. He explains the steps required in order to setup a barebones ES6 project with the help of our faithful tooling companion Gulp.
ECMAScript 6 is the upcoming version of the ECMAScript standard and expects ratification some time around June 2015.
This article explores the creation of an interface component to apply React.js CSS transitions on initial render.
I’ve been using React.js for a little while now, both in my 9 to 5 job and for my own projects, and during that time I have started evolving my own set of React.js best practices.
Of late I have been deep in Angular land and I just thought I’d share a little discovery that I was shown by a fellow work college the other day.
Thankfully these days we have a handful of tools to help with this situation. Let’s examine RequireJS in an attempt to decide if it’s for you… or not.
Of late there has been a little bit of hype around this “webpack” thing. Hopefully this post gives you an overview of what it is, how to use it and if it’s worth all the hype.