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!
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
Client-side APIs on mobile and desktop devices are quickly providing the same APIs. Of course our mobile devices got access to some of these APIs first, but those APIs are slowly making their way to the desktop. One of those APIs is the getUserMedia API...
The MooTools More library is a goldmine. A treasure chest. Pirates booty, if you will (and, of course, I will). More is full of plugins that add a lot of class and functionality to your website with minimal effort.
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
