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 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).

Admittedly I share the sentiment... I don't think there is any viable solution in sight though.

Wow, this is a very good exploration of the performances of several common languages and runtimes. This is one of the most thorough I've seen. A good resource for deciding what to pick.

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.

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.

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).

Interesting use of WebAssembly for fast and very portable code. Also especially interesting is the care in the move to the new software architecture.

Or why upgrades need to happen with care, especially with an open platform like the web...

This is a good way to get into how Javascript engines try to optimize the code thrown at them. It's definitely not an easy job with Javascript...

Interesting way to combine Django and a couple of JS based tiny frameworks to make simpler frontends.

Looks like a tiny and nonetheless powerful library for animations in web frontends.

Similar to RR but for web frontends.

This ecosystem keeps baffling me... How come there are so little checks on what can get published or how the command line process parameters.

At last some interesting tooling for profiling memory usage of web frontends. Clearly this is very early days though, this will get more interesting as the tooling makes progress. Some of the numbers in the benchmarks they came up with in this article are very scary though.

In my question for simpler web frontends, this looks like an interesting library. It's built on Custom Elements (part of the Web Components effort) and is just a tiny bit of Javascript. Sounds neat and tidy.

A nice list of somewhat recent features which made it to JavaScript.

Interesting use of CSS custom properties to make dynamic color schemes easy and manageable for webpages.

Very thorough analysis on the kind of web frontend performances you can expect for most people on mobile. Since we basically need to reduce the footprint of such frontends to make this sustainable again this is a very welcome article.

It looks like an interesting JS framework. I'm not a huge fan of the big ones which force on you how to structure everything... the apparently minimalist nature of that one feels fairly appealing. Of course need to find the contexts where is works and the ones where it doesn't.