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.

Nice CSS trick to make collapsable trees without too much fuss.

Interesting data point about a service moving completely to the htmx and web components approaches. Not all applications are going to see such drastic improvements, that being said the change in team structure alone feels like a very good thing to me (and is more likely to be the constant in such moves).

Indeed, React is a bit too much of the default choice right now while clearly it shouldn't be that way. Let's hope it'll change and something else with more merit will take its place.

Good overview on the state management offer around React. Especially interesting is how it frames the different problems one has to keep in mind to maintain state in your UI.

Interesting opinion. Indeed, as the browsers are packing more features they can deal with more frontend complexity themselves. This is an opportunity to reduce the amount of code in the frontend code at least for some use cases.

This is indeed a nice set of tasks to evaluate a frontend tech or your mastery of it. Potentially usable in interviews?

There is indeed a trade-off approach available nowadays between "backend computes the whole page" and "frontend computes it all in JS". This sounds like an interesting patch depending on the project context.

Good explanation of why the complexity of CSS code quickly gets out of control.

Interesting stuff coming especially on the CSS side.

Interesting set of tips. Indeed that's a good way to reduce quite a bit the complexity of your application web frontend. Might not be always applicable though.

CSS is definitely a rabbit hole full of features. That delays quite a bit the time when you need to use Javascript.

Not the first time I bump into an article about that one. Solid.js is definitely getting close to something I might enjoy using (unlike React which I dislike quite a bit).

This is so true... It's just almost always better to use standard components in my experience. In particular it makes things easier for keyboard navigation and accessibility.

Now this is indeed a very clever CSS trick!

Since the tooling is still far from great for web frontend memory analysis, it's nice to see some effort there.

Now that looks like a really nice CSS framework. I like the approach with a very limited set of classes and pushing you to focus on semantic.