Writing C++ in 2025
andreabergia.com
andreabergia.com
You expect to not have to invest the time and effort to learn a new ecosystem? Just try it out for a week and then complain you don't know it as well as Rust? Almost every single complaint in the article directly stems from the author's lack of knowledge about the tools and language. The fact that the author relies on LLMs to tell them how to configure things really says it all.
And anyway, it was not a particularly serious (or, for that matter, well written or argued) discussion. As I mentioned in literally the first line, it's just a rant :-)
PS: I am unsure what you mean with "relying on LLM for configuring things says it all". In my experience, this is one area where LLMs _really_ do help a lot - it has been much faster than going through the documentation (which I also did quite a bit of, in particular for conan).
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…
The newest standard is C++23 which has std::expected, basically is the same thing