Chrome 67

I really loved the way Lin Clark contrasts the explicit binding of variables between files of code using modules vs. implicit binding where you simply expect that a given variable will be in a certain place within the global scope (like jQuery’s $ shortcut) and how it makes modules not just a better way of connecting your software together but also a way of protecting your code from mistakes.

You might be wondering, “What’s the support for these features? In fact, what’s the support for ES2015 these days?” If you do think that, then don’t forget about the Kangax compatability table: ECMAScript 2016+ compatibility table

Here’s the December 2017 video from the CowtownJS meetup in Fort Worth. I gave the talk this month and I regaled everybody with why they need to pay lots of attention to Web Components now because I think they’ll be what we’ll all be using in the not too distant future.

Note: There are some video artifacts, likely caused by the fact that I was recording with Screenflow and using AirPlay to mirror my display to a large TV in the room at the same time for everybody who attended to see. The audio is good though and hopefully you can see most of what I’m showing pretty well.

Click through to see a slew of links related to Web Components, Polymer, and more.

If the name Mike Bostock doesn’t immediately leap to mind, the project most closely associated with him should. D3.js is the cat’s meow when it comes to doing any kind of visualization work and it has been his baby for a long time.

Now he’s got an interesting new project in the form of an interactive notebook where you can embed JavaScript code directly into the notebook: