I admit I'm tempted to look at Typst more nowadays. It looks like it can simplify the production of content quite a bit compared to some of the good oldies we still carry around (like LaTeX). That said, Typst is still young and not that stable yet.

This is unfortunately still a bit complicated for my taste. Ideally std::simd should be stabilized, but since it's not the case yet options have to be evaluated.

A long needed improvement to Java on its way to the JDK. Looking forward to this one stabilizing.

The trend has been clear for a while. This is a well crafted job of clearly mapping it out. Time for Europe to wake up maybe?

Unfortunately and as far as I can tell we're still not there. I'm trying to do my part in how I push for those topics when working with teams and organizations. So many things to help with on the practice level and making developer teams function properly.

An old introduction to DDD. Not necessarily the best reference on the topic (which is probably still the blue book). Probably a good resource to skim over the important points and get started though.

We can cast doubt on the "Spotify Model" (not really a model anyway...) all we want. Still, I think the whole "guild" idea in there was spot on. This article gives a feel of how it can be setup and the benefits it can bring.

A good reminder that you don't want your code base clean to the point of being sterile. You have to fight off the mess yes, but some of it can stay if it provides affordances.

Neat stories explaining those three important features of Python.

Indeed, if we weaken the learning loop by using coding assistants then we might feel we go faster while we're building up the maintenance cliff. We need to have an understanding of the system.

I use it mostly from the DAV integrations, so I don't notice this much in practice. That said, if and when I have to use the web GUI, it indeed always feel sluggish to me. There might be a reason behind it indeed, those bundles seem way off.

A larger transition coming to HTMX. Interesting choices and good lessons on how to manage the API transition.

Very interesting maturity model about proper communication in a remote work setup. I think it definitely makes sense and doesn't feel too difficult to evaluate.

We take text rendering for granted. That said, it's easier said than done, especially on the GPU.

Yes, same here I way prefer email (even though messaging can have its uses of course).

There's indeed value at using the URL to store some of the frontend state. This is too often forgotten.

Just use the semantically appropriate HTML element. It makes it easier for browser to advertise the GUI properly.

A bit of an advertisement toward the end. That said, the evaluated constraints are completely valid. You don't want to fit your whole code base into the "cloud function" model, only a few workloads will make sense there.

Looks like an interesting tool to go with mise.

Nice little website advocating for more use of the XDG base directory specification. This is still needed to push for it indeed.