Nice to see this effort keeps bearing fruits. This is a very needed engine to avoid a monoculture.

Good reasoning, multi-page applications should be the default choice for web frontends architecture. The single page applications come at a cost.

Interesting, "state of the union" regarding local-first we frontend. Lots of pointers towards other resources too.

It's clearly not clear cut, it's a whole spectrum. I wish more web developers would at least ask themselves the question before having knee-jerk reactions reaching for their favorite framework of the day.

Nice reasoning. It very well highlights the tradeoffs coming the choice they made. And of course the decision might change if the situation changes.

Interesting analysis around the current situation around web scraping and intellectual property. This moved to being mostly dealt with using contract law which makes it a terrible minefield. Lots of hypocrisy all around too which doesn't help. GPT and the likes will likely be the next area where cases will rise.

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.