Another library of web components. This seems to pick up and it's welcome.

Interesting set of advices. There are a couple I tend to disagree or doubt they really matter though. Other than that probably worth keeping in mind.

This obviously keeps progressing. I think a good resource summarizing the new ways to do things would be necessary.

Very cool idea. Lots of history in there! There were things I even forgot about.

Interesting exploration of the performance for web resources when they're bundled or not. Also dabbles in the reasons behind the exhibited performances, definitely to keep in mind.

If you got to implement an OAuth integration. Please be responsible and don't do this... this could lead to very serious breaches for your users.

Nice explanation on how to handle request errors with HTMX. It's in fact relatively simple even though there's a couple of pitfalls.

Long article in two parts (make sure to read the second one as well) showing how to build an interactive painter with CRDT. Nice way to understand how they work.

Very interesting computational geometry tricks. You can make interesting shapes out of this.

A bit basic and obvious, still a good list of things to keep in mind when designing REST APIs.

Nice and fun little demo of what can be done with CSS animations.

Fun way to understand better the CSS layouting using flexboxes.

This is a good way to manage your website. I do the same regarding my blog, I don't do any analytics etc.

This is an interesting use of the accessibility directive for better styling in web frontend code.

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.