Looks like a neat software library for procedural geometry.

I strongly agree with this piece. There are very interesting web frameworks out there. They should be evaluated on their own merits but are too often just ignored.

Looks like an interesting alternative to the bigger Django and FastAPI which get all the attention.

Good followup to a similar piece from someone else about React. Frameworks with a short half-life are not worth the hassle to learn, focus on more fundamental skills instead.

Good advice, no one should be a "React developer". Make sure you learn more fundamental skills.

This is definitely true. As long as web frontends are dominated by large frameworks, the web will always have subpar experience on mobile. And the solution isn't going to come from the mobile providers too happy to gatekeep their app store.

I very much agree with this. The relationship between developers and their frameworks is rarely healthy. I think the author misses an important advice though: read the code of your frameworks. When stuck invest sometime stepping into the frameworks with the debugger. Developers too often treat those as a black box.

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.

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.

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.

Don't believe too good to be true marketing claims by vendors. Clearly something went wrong there and the benchmark has been gamed.

A bit messy sometimes and a few arguments seem weak to me. Still the core message holds: don't let a framework rule your project.

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.