> Let’s talk about the real stuff: writing C++ in 2025. Naturally I have tried to use the most recent standard, C++20, which has innovative new features such as

> Let’s talk about the real stuff: writing C++ in 2025. Naturally I have tried to use the most recent standard, C++20, which has innovative new features such as formatting a string without sprintf, using std::format C++23 has been around for 2 years, many features are support by most compilers (ahem std::expected)… > Let’s start with the simplest of things - needing both a .cpp and .h file. I’ve heard modules were a thing, but googling a bit showed that they aren’t really working properly yet, so I ended up not even trying them. They work fine, the issue is with clangd and even then clangd-19 works fine with modules. The most annoyance I have with C++ is that it still expects the stdlib to be dynamically linked, which means packaging is a pain and there’s no tooling to make it easier. Would I write a side project in C++, definitely, my side projects tend to pull in a ton of C libraries that do not have good alternatives in rust. If I don’t need to pull in C libraries I probably don’t need the annoyances of managing memory and lifetimes and I’m writing my code in golang… I have to found the niche where rust is the right tool for the job in my narrow corner, there are places where it is but for me there are the yet. And I can call C code from golang pretty easily as well…