On this week's episode: David starts the show by revealing he has a headache and an hour of discussing JavaScript tooling will not make it better. The show covers the history of JavaScript tooling (from nothing to JavaScript loaders, minifiers, webpack, and more), the pitfalls of popular tools, and the future of tooling. Enjoy!
Next Episode: Q&A!
Todd and I would like to host a Q/A session where we answer your questions! Please tweet us your question and we'll answer them on the next show! Cheers!
CSS and JavaScript: the lines seemingly get blurred by each browser release. They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely. We have our .js files and our .css, but...
While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready? Promises are becoming a big part of the JavaScript world...
One of the great parts of MooTools is that the library itself allows for maximum flexibility within its provided classes. You can see evidence of this in the "Class" class' implement method. Using the implement method, you can add your own methods to...
One of Dojo's major advantages over other JavaScript toolkits is its Dijit library. Dijit is a UI framework comprised of JavaScript widget classes, CSS files, and HTML templates. One very useful layout class is the TabContainer. TabContainer allows you to quickly create a tabbed content...
