Looks like I'm not alone advocating for commits which tell a story. Makes reviews so much nicer.

If you're wondering why the architecture is called "amd64" and why the itanium disappeared... this is why. It was a very good stunt from AMD back then.

There's some truth in this piece. We never quite managed to really have a semantic web because knowledge engineering is actually hard... and we publish mostly unstructured or badly structured data. LLMs are thus used as a brute force attempt at layering some temporary and partial structure on top of otherwise unstructured data. They're not really up to the task of course but it gives us a glimpse into what could have been.

Indeed they did plan ahead very well. It's no surprise if Postgres is doing so well this days.

Nice overview of where we stand regarding supply chain security. Code reuse has never been so widespread and we still have fundamental issues leading to security problems.

Just a little dive in the Rust standard library. It gives a good idea on how they pile layers to ensure safety while providing a nice API on top.

The European Commission plans are indeed short sighted... Hopefully they'll come to their senses and prioritize funds for FOSS.

I don't think that's the only challenges but those are indeed two good things to keep in mind to ease the syncing.

This is really a funny idea. I admit I'm curious about what it contains.

Indeed, stress can't be completely eliminated... but at least build an environment where risky situations are reduced as much as possible. So that when stress or anxiety shows up you can take notice and react. Otherwise you'll be creating vicious circles.

Apparently in the age of people using LLMs for their tests, there is a bias toward mockist tests being produced. It's a good time to remind why you likely don't want them in most cases and limit the use of mocks to consider fakes and checking system state instead.

When the European tech regulations encounter the changing geopolitical landscape... can we expect sparkles or the European Commission will cave in? I honestly hope it's the former.

This is definitely true. Keep all this in mind when dealing with performance questions: design properly for the task, profile and profile some more, focus on the hotspots, keep things maintainable.

I don't think it's always unfolding exactly like this but there's some truth to that. Most projects see a "let's rewrite it in X" phase, this is rarely the best outcome.

Of course I agree with this. We should fight undue complexity at every step. This beast tends to creep up very quickly and we're all guilty of it at times. This is indeed particularly obvious in otherwise rich languages like C++ or Rust. Those tend to push people to try to be clever and show off, often for "performance reasons". This is rarely a good idea, think twice.

I would have titled the "defer refactoring" section differently though. Probably "defer abstracting" would have fit the bill better.

This latest development in the Ruby community is rather concerning.

Definitely a good move to have more sustainable income for Mastodon.

Let's have some well deserved praise. The product is definitely good, the community is great. Who said I'm biased?

Looks like we got a new and interesting language for configuration. Might become a nice alternative to yaml and its traps.

Clearly a big step in Blender history. I wish them success through this transition. Blender is a very important and influential product in its space.