Nice little primer about Elixir and Phoenix. Be careful though, I spotted a couple of mistakes in the code examples. That still gives a good idea of advantages and limitations of this stack.

Good balanced view about Web Components. Interestingly it seems the adoption is already higher than I expected.

Long post but worth the read in my opinion. It lays out good reasons for reducing the dominance of React and move beyond it. There are good reasons to do so, and they're piling up with the time passing.

Good thinking about abstraction levels on top of a platform. It's very much focused on the Web platform but applies more generally. Good food for thought on the libraries vs framework debate, why escape hatches matter and why you want a layered architecture.

Good reminder on how the W3C works and what it evaluates. If Web Environment Integrity would become a "standard" it'd likely be more of a "de facto" thing because a major player shoved it everyone's throat.

Nicely explain how to secure your webhooks step by step.

I admit I'd love it if it made a come back. That'd be a big boost to self-hosting websites for people. Our infrastructures are not quite ready for it though.

Indeed, too many websites or apps break or hijack basic features of the browser. To me it also shows the tension between trying to have a document browser and an application provider shoved in the same GUI.

A little experiment which turns into a neat reference in HTML elements. Could be useful.

Interesting point of view. We have two worlds now coexisting on the Web and they tend to ignore each other more and more.

Nice recounting of the first meetings to make the web what it is today.

I think this is the right way to look at the problem space. The analysis provides the right pros and cons to look at when picking a frontend framework.

Interesting list. Definitely to keep in mind when developing and deploying a web application.

This is indeed looking more and more like a viable and worthwhile option for web applications.

Nice overview of WebGPU. Also does a decent job laying out the history of graphics APIs. With WebGPU bound to be more widespread and available outside of the browsers things will get very interesting.

Indeed, without deciding to put everything in the public domain, the face of the web would have been very different.

I must resist to redesign my blog I guess... In any case, this is a very nice style for content.

There are many more useful codes than are generally used. We shouldn't shy away from using them when it makes sense, it also means the client side must be ready for them. Very often client code makes wrong assumptions on the possible codes.

This is really a huge update. Brings in lots of features which were clearly missing.

Interesting tool... this is generally done with tools where you're captured into a GUI. Moving this to text and static generation opens the door to proper versioning etc.