It's just impressive what we can achieve with instanced rendering. Even the mobile web browsers support it nowadays.

Excellent profile of Tim Berners-Lee.

Go and read it! It'll give a lively impression of the Web early history. It's amazing how, back then, he managed to fend of the greed of corporate interests in order to make sure his original vision would survive. Of course not everything materialized, most notably the Semantic Web (sadly).

Nowadays, the real question is the fragmentation due to the big closed platforms power grab and the political context. Can we still save the Web? For sure there's no clear path yet.

There's some truth in this piece. We never quite managed to really have a semantic web because knowledge engineering is actually hard... and we publish mostly unstructured or badly structured data. LLMs are thus used as a brute force attempt at layering some temporary and partial structure on top of otherwise unstructured data. They're not really up to the task of course but it gives us a glimpse into what could have been.

A tiny piece of history which was instrumental in the way the web and email developed back then.

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.