Indeed, teams reach out to Yocto by default a bit too much. It's good to have an idea on when you really needed and when you can go for simpler options.

Good point indeed, need to review my own feed next time I get the chance.

Good point, the booing on Eric Schimidt's commencement speech is likely not just about him talking about AI at some point. You see, the man has very heavy baggage... He's one of the architects of the current dystopia but won't acknowledge it.

Very interesting take. This gives very valid ground on why tech communities should reject AI based contributions. Not doing so will indeed hinder the commons communities rely on to exist and improve. This is a path to prevent getting better at inclusivity and diversity (which is really needed).

The writing isn't perfect, but it covers quite a few important topics in Rust. Seems to be a nice resource even though it's still work in progress.

This is clearly the Ouroboros moment in our industry. People pushing for such restructuring and layoffs are drinking the kool-aid and will ultimately be responsible for killing what put them there in the first place.

I mean, with the announced productivity gains of generative AI... It doesn't feel like a big ask. 😜

This is very concerning. We don't need Wikipedia to fall prey to this kind of tactics... On the contrary!

Wondering about the memory layout emitted by the compiler when a virtual table exists for a type? This is a good summary.

Good post to have an idea of the modern IO APIs available.

Interesting point... Didn't think about it this way. We'll see I guess. Maybe human made services will actually get a premium rate indeed. Wouldn't be a bad outcome I guess?

This is an odd and unexpected one! Funny after the facts bit clearly annoying otherwise.

I guess it's time we realise Google doesn't send much traffic on the open web / small web / indie web (call it as you please) and so there's no need to let them harvest.

This is a fact I don't get... people are going their way to satisfy the need of a LLM but not the ones of fellow humans. I guess it's the conclusion which is somewhat right, it's about who has power. This is sad if true... also I doubt it's the single explanation.

Microsoft has been deploying new CA certificates late... Now distros have to wake up and prepare new signatures for their shims quickly.

With Bitwarden sinking, it's maybe time to look at alternatives? This AliasVault option looks like an interesting contender even though a not young.

Sounds like a good solution to self host things at home while having some protection.

Or why most of the studies we see out there can't be trusted. They're full of holes and flaws. We'd really know people who know what they do in humanities to conduct such studies to get a chance at a proper picture.

The title is a bit too much of a blanket statement. Still there's indeed a lovely no between pair programming and merge requests. If possible you should favour the former. Yet it rarely happens in practice, there are reasons for that.

This is a good point. I feel unease at the current trend pushing toward cooldowns. The proposed rollout scheme is much better and fairer.