There's always an interesting lesson in this kind of failures. Here clearly it is in part a story of unchecked trust, and not planning for a bigger system. It came with real consequences too.

Obviously the essay from Peter Naur keeps popping up lately. It feels like an important piece, especially in the current atmosphere of vibe coding. This article lays out quite well why vibe coding is the opposite of what we should be doing.

This is (IMNSHO) a very important open letter. This confirms to me that the whole set of age verification laws we're seeing popup everywhere is severely misguided. Had my suspicions before of course but it's getting clearer with this one. We should stay clear from those laws as a profession, it's important to not comply, it'd be a disservice to our users.

We should indeed put an end to those proprietary formats. It's sad to see the EU Commission contradict itself there.

A good illustration of making illegal states unrepresentable. This definitely helps with code safety.

This is definitely a cool project. I like the idea.

Probably somewhat self serving so the numbers would need to be confirmed with other experiments. That said that case gives a good idea of the price in terms of complexity and resources when choosing to go for an SPA.

Interestingly the issue for the compile time is not so much the feature itself but the STL headers required. It makes PCH pretty much mandatory.

Interesting piece which challenges the shared-memory vs. message-passing dichotomy. It message passing indeed gets rid of data races but nothing more. Of course this is nice already, but that doesn't mean you can't have the other families of concurrency bugs creeping in.

Those dangerous and stupid laws keep popping out unfortunately. This is clearly a slippery slope as shown from the New York bill... We need to push back or the demands will keep growing. Let's hope Free Software communities won't try to preemptively comply, this would be short sighted and self-sabotage.

This is concerning, hopefully the amount of issues which get through will be limited.

Yes, Rust like C++ comes with zero cost abstractions. Still they can get in the way of some compiler optimisations. This is an interesting case preventing vectorisation.

Rampant complexity in software is also a management issue. Are we sure we're rewarding the right things?

A reminder that logs are not for the developers first but for operation.

You probably want to complete this with a higher level plan if the goal is a larger modernization. That being said, it's a good approach for mid-level to small goals you'd want to tackle.

Yes there's a dip, but this piece presents compelling evidence that it's not the death of literacy we're sometimes screaming at. It is also a love letter to reading and writing.

Wondering how udev communicates with the kernel? And then broadcast events? This covers the basics.

What could possibly go wrong? This is really a weird appointment.

Didn't know about this one. Looks like a nice alternative to the venerable man command.

The stupid idea of age verification keeps spreading with ridiculous laws...