WDRL 241

Doodles, Chrome 70, Print Link Lists, JavaScript == CO2, and Data Scientists

Hi, I’m Anselm Hannemann. Freelance webdesigner, frontend engineer, advisor. Curating WDRL, growing vegetables on a market garden farm.

Profile photo of the author, Anselm Hannemann


it’s an interesting concept to compare JavaScript with CO2 and yet a very valid one. Alex Russel who works for the Chrome team and has a lot of insights into the current state of the web says that using too much JavaScript or using it exclusively (without progressive enhancement / graceful degradation) will have the same effect as too much CO2 for the ecosystem on planet earth—the ecosystem falls apart. And while we also need a certain fair amount of CO2 on the world to live, we need JavaScript on the web. It’s that fine line that makes the difference—not too much and not none.

I feel that with the native browser APIs that we have these days we have a great opportunity to build great web services without bloating them too much and without relying only on JavaScript. We can enhance native elements with Custom Elements API easily via ES6 Classes, with so little code that it seems ridiculous to build all that on your own in a third-party framework. Coincidentally, the Github engineering team has published how they dropped jQuery now entirely and what they now use instead—native JavaScript and small, lean code that is progressively enhancing their platform—with less code, better maintainability and more stability.



Web Performance



Go beyond…