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

Friendly reminder that the term "server-side rendering" doesn't make sense. Also, you don't have to use React of the likes on the server side, it should be as simple as making string joins indeed.

It becomes clear that there are more and more reasons to move back to simpler times regarding the handling of web frontends.

Nice comparison of both approaches. Some of the criteria used I would have left out but otherwise it seems fair.

The idea is interesting even though it probably needs to mature. It's interesting to see this kind of libraries popup though, there's clearly some kind of "backend - frontend split" fatigue going on.

Another nice list of defaults for SQLite. Some of them I didn't have on my radar.

Where are the limitations of using SQLite in production for web applications? Here is a good list.

The right and wrong approaches for paginating results coming from a database.

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.

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

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

Interesting points about soft deletion... its usual pattern might not be what you need in the end. The proposed alternative is interesting to keep in mind.

The tone of the article isn't exactly to my liking, sounds "too good to be true" at times ignoring important details driving the choices (despite some warnings early on). Still, depending on the amount of data stored in your database, SQLite looks increasingly viable on the server, replication even coming down the road.

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.

Looks like it's still in the very early days but the overall approach looks interesting.

Stay away from the hype and introduce complexity in your systems only if it's warranted by the problem space you have to tackle. Most organizations don't need microservices, use them responsibly.

Excellent reminder of how awesome strace is. This is one tool every developer needs to know, it often saves the day when everything else fails.