Interesting take on building software that lasts. I'm not sure I'm fully aligned with this but its good food for thought.

I strongly agree with this piece. There are very interesting web frameworks out there. They should be evaluated on their own merits but are too often just ignored.

Interesting, there are definitely some trends benefiting saner alternatives... But are we really seeing the end of the big social media platforms as we know them? Let's wait and see.

I think this effect is a usability nightmare. That said it's interesting to see which CSS and SVG tricks can be used to simulate it. This opens the door to other effects.

This is nice to see the energy still bubbling in the traditional web. It's still there, next to the big mall pushed by search engines. You just need to know where to look and it's not that hard.

This is already an old article now. Still the core of it still rings true. The optimistic note at the end of it didn't come to pass though.

We got many options nowadays. Most of them are likely better than just making the underline disappear on links.

The idea is interesting... Seeing how the search engine space is degrading quickly I'm tempted to try this actually.

Long but thorough collection of all the nice improvements CSS brought the past few years.

Lots of good points in there. Very much focused on web services APIs, that being said the first part also applies to libraries APIs in my opinion.

Here is another point of view on the XSLT situation in the WHATWG. Clearly the process needs to be made clearer. I'm not necessarily convinced by everything which is brought forth in this piece, still nice to have different point of views on it.

Or why the XML roots of the web are important to keep in shape. I'm not necessarily in love with how verbose XML is, but it's been a great enabler for interoperability. That's indeed the latter reason which pushed Google to try to get rid of it as much as possible.

This is a good list of guidelines to produce a service which is less of a pain to test locally, deploy and operate. Of course, don't take everything at face value (not all of it aged well) but it's a good source for inspiration.

Looks like an interesting alternative to the bigger Django and FastAPI which get all the attention.

And it's not necessarily a problem. It all depends on the goal and context of the API you're building.

Good followup to a similar piece from someone else about React. Frameworks with a short half-life are not worth the hassle to learn, focus on more fundamental skills instead.

Friendly reminder that the term "server-side rendering" doesn't make sense. Also, you don't have to use React of the likes on the server side, it should be as simple as making string joins indeed.

I'd like to see the equivalent for Europe. Clearly in the US things aren't always great for Internet access. The latency is likely higher than you think, and the bandwidth lower.

A bit focused on web frontend, but that applies equally to other stacks. There are many reasons to make UIs accessible.

There's clearly something tempting about a web index somehow separated from Google. It always felt like a natural monopoly and so a type of public service.
Now that push arrives a tad late so the impacts are unclear. Overall I still think this would be a net positive if there are more web search companies built onto such an index.