Interesting work from Apple and Google to have better hardening in libc++. It's nice to see it ripples through the upcoming C++26 standard as well.

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

OK the coming compile time reflection features coming with C++26 are definitely mind blowing. It really opens the door toward a very different evolutionary path for C++. Many things can be done from libraries now and producing bindings to other languages shall become much simpler to.

Now it's once again about adding more to the language... This makes the question of how to extract a safer and leaner subset even more important. It's also asking for more tooling to support it, like the constexpr debugger mentioned during the questions.

Yes, this one feature in the standard doesn't seem to reap much benefits... It's sad that it got there.

Excellent news on the PNG standard front!

OK... This is weird and funny. I definitely like the idea of an actor reading this important RFC aloud.

Looks like the protocols landscape for writing LLM based agents will turn into a mess.

I have a hard time seeing browser makers truly drop third party cookies without pushing a worse replacement first... Still, it's nice to see the W3C take a stand in the matter.

Nice post about the practical impacts of Postel's law. It's especially problematic in the case of Open Source software. Companies producing proprietary software even use that to their advantage.

This could be a big improvement for C. We'll see how far this goes.

A nice glimpse into the maze of the escape codes on the terminal.

Parsers are required to normalize URLs but often they just don't. To be kept in mind in your code.

Yes, please let's increase the market share of non-Chromium based browsers.

Looks like C++26 is going to be a big deal. The reflection and generation features alone are going to be a game changer. Now if it also gets contracts it'd be really nice.

From the perspective of a given implementation. Still this is a good list of what POSIX 2024 changes. I'm particularly interested to see that per-file-descriptor advisory locks finally made it to the standard. Still some progress to make in this department but it's a good step already.

Interesting stuff coming in that space, but at a very slow pace. This is unfortunate since it makes adoption slower too.

An old article, but a fascinating read. This gives a good account on the evolution of POSIX and Win32. The differences in design and approaches are covered. Very much recommended.

It's good to see this initiative keeps thriving. It's the best way to ensure the standard is well implemented everywhere.

Finally a standardized protocol for end-to-end encryption! Let's see where this gets used.

Definitely this, use standard locations as much as possible. We can tame the mess of dotfiles in user homes.