Links For You (11/22/26)

Links For You (11/22/26)

Happy Slaughter of the Turkeys week, or Thanksgiving if you will. I'm usually pretty honest about what's going on with my life, good or bad, and with that in mind, the past few weeks, and some time before that, have been pretty bad. I'm not going to go into why, but I will say it makes me so incredibly appreciative (and thankful of course), for the people around me. My friends, my family, and most of all my wife help keep sane. Well, relatively so. ;)

Here's some links for what will hopefully be a quiet week. Happy Thanksgiving!

Developer Slides

I've been a Reveal user for years. It makes it easy to use HTML to create web-friendly slides. It's great, but I ran across Slidev a few weeks ago and it looks like a great alternative. It's Markdown based and has a CLI for scaffolding as well as exporting to PDF, PPTX and other formats. You can even use a built-in interactive editor in your browser. It's been a hot minute since I've given a presentation, but I plan on using this next time.

You may not need NPM...

Of course you need it, I'm just being silly. But this great post by Flavio talks about additions to Node.js that replace common npm packages: Node.js built-ins that replaced npm packages. He goes through multiple different packages that have built-in support with Node now, but also discusses why you may still want the existing packages. I've said this for years now, but with so many npm packages out there it's easy to forget what's available in the platform itself, and Node's certainly been advancing at a rapid clip over the years.

Did AI kill web components?

I'm a huge fan of web components (you can peruse my many posts on the topic if you want), but in this post by Nolan Lawson, he argues about their future in an agentic future: Do web components have a future if nobody is writing them?. Nolan is dang smart, and he makes some really good points here. There's a few quotes I think that particularly stand out:

In short, web components were designed for a world where people typed HTML by hand, code was scarce, and thus reuse was an economic necessity. None of those things are true anymore, or at least they’re much less true and becoming less so by the day.

And this bit:

Still, I think the strongest argument of all is that neither web components nor React nor any other framework really matter, except maybe as a footnote in someone’s AGENTS.md or an aside in an agent’s thinking process. Recently I vibe-coded a small app for my wife, and the agent mentioned that it was wavering between Preact and Svelte before finally settling on Preact. To be honest, I didn’t care at all because the app worked and solved the problem at hand.

I think Nolan is pretty spot on, and it's not a "web components are dead" take but rather, not necessarily the as useful in the agentic era. Definitely read his post, and at the end, he links to a good response post as well: On writing the custom elements section for Modern Web Guidance.

Just For Fun

I'm skipping the usual music video and instead sharing an incredibly cool demo called Night drive. It's a drive... at night... but all done in a web browser and gorgeous to look at. The app also does a great job of explaining how it's built with interactive controls to let you tweak how it works.

Screen shot