Better late than never I guess? Let's just hope this becomes very costly for that evil company.

This piece is strongly worded but the logic is sound. We see many examples of power plays in guise of "innovation" which lead to killing openly sharing (and so killing real innovation). It's urgent to fight back and ensure things stay open.

So many requests based on vanity and hype... I like the question "when you go to other websites do you use it?", we should use it more. Maybe at some point we'll realise that simplicity matters.

It totally makes sense. If you're a FOSS project you have to invest in getting more long term contributors, which requires mentoring. The contributions themselves are not something to maximise. I wish more communities would follow that path.

It's an interesting trick for personal tooling. Keeps things really simple to setup with limited code to maintain.

Looks like some governments noticed that they can move away from GitHub and are testing the waters. Good idea!

This is indeed time to move away from GitHub if you're still there. There are many viable alternatives.

Good first half of the post, there's indeed more paths out of GitHub than jumping from a centralised system to another one (even though Codeberg and Forgejo are much saner from a governance standpoint). We'll see what the future brings.

There is clearly a sweet spot around 60 fps. Beyond this... You quickly end up in cargo cult territory.

Straight from the uutils rewrite. This is interesting both for the class of bugs which made it (very system integration oriented, unsurprisingly) and the ones which didn't appear at all (anything to do with memory).

A bit of a stretched metaphor in here, but indeed being individually faster doesn't automatically make the team faster. Sometimes quite the contrary in fact.

A good illustration that you can beat classical algorithms by taking into account how modern CPUs are designed.

Want a primer on email routing? This is pretty much it.

It all changed so much! That's quite a journey for our field. Of course it's not over yet. At some point we'll be real engineers I guess. 😉

This is a good illustration of how flexible and expressive Lua can be. Gives ideas to make DSLs.

C++ too can have its own supply chain disasters with enough effort!

Another post which shows that the right technical job interviews are the ones creating a real conversation. It's the only way to have a chance to figure out what the candidate is made of.

This could be a piece full of nostalgia. There is a bit of nostalgia of course, but it's also a path to use what we got in a more valuable and humane way.

This part of the industry is struggling more and more (or more likely silently taking more risks to hide the struggle). It has no path to sustainability and it starts to show.

Indeed, the memory layout of your structs can matter. Be it Rust or not, but in the case of Rust the use of Option might give the wrong feel about the resulting layout.