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.

Facebook getting interested in the fediverse indeed looks like XMPP or OOXML all over again. Beware of those old tactics, they are very efficient against communities.

This is a very concerning for C... and it drifts apart from C++ further. The old "C as a subset of C++" position is less and less valid. Very unfortunate.

Interesting warning about too early standardization. Don't go top-down, better go bottom-up working on each separate problem and see if something emerges.

A good reminder of what the Web really is. Yes, it's hard to add features to it, but look at the amazing backward compatibility! Everyone can write web pages and that's what matters.