WDRL 199

The issues with CAA-Checks, IntersectionObservers for scroll events, a matches-selector for CSS, and mining crypto currencies with wind energy

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


We’re in a very diverse work environment: As web developers we have countless options to specialize in but it’s impossible to keep up with everything. This week I read an article where the author recognized that even though he has been building stuff for the web for over seven years, he’s not able to understand what he does, summarized in this sentence: “I’m slamming my keyboard in frustration as another mysterious error appears in my build script”. For the author, it’s no fun to write JavaScript anymore today as the tool chain got too complex, the workflows are built mainly for developer convenience and many things that exist in the languages itself are reinvented in external libraries.

Now when I look at what articles I have for you this week, this seems very understandable. Soon we cannot use .dev domains anymore, HTTPS CAA checks do not work with private network interfaces, and when I look at an admittedly great tutorial on how we can replace scroll events with IntersectionObserver, I see code that might have better performance but definitely is more complex than what we used to do with EventListener. Our incredibly fast-changing environment expands very fast and we need to acknowledge that we as individual persons can’t know and understand everything. And that’s fine. Choose what you want to do, be sure on priorities, and then hire someone else for the remaining priorities you can’t do on your own.







Work & Life

Go beyond…