Matthias Ott asks the very good question: What’s Too Good to Be True?

Which of the [web platform] features that got shipped in the last few years have actually proved to be the most valuable? Which features do you use all the time? An interesting question to think about for a little while…many of the features we now take for granted actually almost sound “too good to be true”.

As grumpy developer nerds, we can spend lots of time complaining about and arguing about the features we don’t have on the platform yet (or haven’t yet rolled out in all browsers), but it’s helpful to take stock of what we do have today and appreciate all the progress made thus far.

Something I’ve always loved about the fundamentals of the web—HTML & CSS in particular—is that they’re so easy to use as well as abuse. You can throw all kinds of random goofiness at browsers and they’ll valiantly trudge along, doing their best to render everything despite the errors. I recognize this isn’t appreciated by all, but that sort of fault-tolerance is arguably one of the reasons the web became so ubiquitous.

I’m critical of Netlify.

Earlier this year I provided some context on The Spicy Web blog in My Journey Away from the JAMstack, and then I got a chance to speak to some of those points in the Jamstack ZHUZH Community Round-table. In a nutshell, I think Netlify’s marketing has become (more) intellectually dishonest in recent years. It’s a shame because once I would have said Gatsby was the most intellectually dishonest framework/hosting company in terms of its marketing. Perhaps not surprising then that Gatsby was eventually absorbed into Netlify… 🫠

One of the things I love most about all this new talk concerning HTML Web Components is how much focus there is on vanilla DOM APIs.

For example, in this demonstration by Raymond Camden, it shows how to progressively enhance a link with an image tag so that you can click on the thumbnail-sized image and see a full-size image in a dialog (using <dialog> of course!).