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.

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

This is clearly getting more mature. Even the list of issues presented here actually makes me want to try it more as to evaluate the exact impacts.

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.

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

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.

OK, that looks like an interesting idea for the frontend bits if your stack is mainly Python based. Still very young though.

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

Interesting algorithm for generating image placeholders.

Very nice approach to avoid the font bloating on the web. I'm slightly concerned about the maintenance over time but at least it has proper fallbacks and the fonts used seem widespread enough (for now).

Nice exploration of Django + HTMX + web components for a CRUD use case. Interesting insights and highlights some of the limitations with HTMX.

A bit of a rant so brace yourselves. Still, it's very much aligned with the current backslash against "everything must be an SPA" trend and makes very good points on how it happened. This indeed turned into a popularity contest based on false premises. Meanwhile... complexity increased dramatically on the web frontend side and the performances are bad for most users.

A bit of a rant, but even though React is well established at that point and here to stay (shake a tree and half a dozen React developers fall from it), it doesn't mean it can't be criticized. It does a good job at listing the main ergonomics problems React is suffering from. The funny part is towards the end, the envisioned solutions for another framework look eerily familiar to a Qt developer, it talks about signals and what looks like property changed notifications. :-)

Nice demonstration that web frontend can and should be organized like a regular GUI application (like a desktop application for instance). This will bring the same benefits in term of maintainability and modularity.

Looks like a nice editor to use in web frontends.

The article is a bit confused about what is really about SPAs in general or React in particular. Still it is clear they raise questions regarding accessibility and navigation. In turn, this requires a lot of careful implementation to make sure the user experience is acceptable.

This WebGPU framework is getting interesting. Definitely something to keep an eye on and evaluate for productive uses. Obviously requires WebGPU to be widely available before banking on it.

Looks like an interesting frontend stack. Still young but probably worth keeping an eye on.

Nice guide, the interactive parts definitely help. Good way to improve CSS use.