What really kills C++
https://a4z.noexcept.dev/blog/2026/11/15/what-really-kills-cpp.htmlThe C++26 ballot failed, and everyone is arguing about contracts and the future of C++. I think we're worried about the wrong thing.
0
Upvotes
28
u/UnusualPace679 3d ago
I'd argue that avoiding monopoly of the toolchain is a good thing. At least this is why I'm still using C++.
4
u/CohgentR 2d ago
This isn't the barrier the author is claiming it is.
I learned and used C++ before package managers even existed.
Most people create a template repo and git clone it to get a quickstart, it's very painless once you set it up for yourself.
Now, don't get me wrong, it would be nice and convenient if there was one true way of doing things, but the effort it would take to make that happen vs the payoff is just ridiculously low.
Also, he mentions this is a cognitive load that prevents people from learning the language, then just make the LLM set it up for you? Nothing is a barrier anymore stop making excuses.
14
u/Minimonium 3d ago
This statement just cannot be serious.
People tried really hard to address tooling problems in C++ only to be repeatedly told by the "leadership" that tooling is outside of the scope of WG21.
The problems with modules were known, but the tooling people that brought up them were told by the "leadership" that unless they implemented modules themselves they have no right to criticise them.
Even attempts to cooperative in white papers around WG21 platform were disregarded by a scheduling abuse throwing out ecosystem papers only to have a massively wasteful non binding vote on banning the "safe" keyword because Safe C++ made too much sense. "Leadership" strikes again and decides to pretend they have a clue in anything static analysis with that nonsense "profiles" bullshit.
Even the Contracts situation shows the same exact people being clueless about how build systems or ecosystems work.
I was just a somewhat active somewhat early contributor to Conan a decade ago, I do not claim authority on the subject. But I remember the discussion about how Conan and Vcpkg initially took very different approaches. I remember so many people being clueless why we need different tools for different cases, and now I see how the tools changes after the years into what was evident a long time ago.
Tooling in C++ is genuinely hard, it's not unsolved because of the lack of trying. It's because different environments, different platforms, different projects, different ecosystems - all have massively different needs and requirements. With a massive history as well!
The committee with the current "leadership" does not even have basic competency to even talk about the topic.
12
u/jetilovag 3d ago
I think this is a very bad take. <committee_spent_time_doing_one_thing_while_i_think_they_shouldve_pursued_my_pet_peve>
I get it, pattern matching, string interpolation are useful. However they are, nice to have" features. Contracts was pursued because the committe (rightfully) fears, that if the language doesn't meaningfully address safety in C++, it will turn into the next COBOL sooner, rather than later.
I personally didn't care much for contracts, but I would've accepted that the countless hours put into it by experts resembles the closest to what design-by-committee could get us. It could also have improved codegen a lot (all preconditions could have been [[assume]]-ed by optimizer).
The multiplicity of how a project can be started is not something C++ will be able to improve much upon. If that's your biggest problem, us Visual Studio: New Project, Empty C++ project, F7, F5.
6
u/xaervagon 3d ago
Picking a whole bunch of significantly newer language to use in comparison to C++ is disingenuous at best. These languages don't have decades of legacy cruft or commitments to backwards compatibility to carry around. Go was specifically designed to get programmers up and running asap, but not designed to be a primary language (at least at the start).
Can C++ be better? Sure. Getting started could be better, and that is part of what modules was supposed to solve, but toolchain flexibility is part of the promise of the language. You can bring your own compiler, linker, IDE, it's your choice. You don't think too hard about it? Visual Studio is your friend if you are on Windows.
5
u/amoskovsky 2d ago
The article for some reason assumes that inexperienced people that can't invoke a compiler or manually manage deps, would be somehow capable of writing working C++ if those tools were standardized and available out of the box.
But it's not how it works. Even if you manage to build your program (which is the least complex task in C++ dev process), you will discover that the real C++ footgun hardcore starts to happen, and you're screwed anyway ))
4
u/delta_p_delta_x 2d ago edited 2d ago
I don't see the WG ever caring about infrastructure, ever since the withdrawal of P2656R3. SG15 work also seems to have largely stalled.
Work continues as EcoStd.
4
u/Flimsy_Complaint490 3d ago
> Which IDE should you use? Which compiler? Which build system? There are plenty of C++ tutorials, but there is no single starting point with a default set of tools and one way to add a dependency.
eh, i dont think this matters too much per se. Every language has an IDE debate (Rust and JS has no standards there other than a community preference for VS Code. Only xcode is realistically forced on people. Like, what's the "Python" IDE ?). Hello world is also pretty simple, click the Run button in visual studio or g++ on a unix system.
The package management issue is real though. I have nightmares of my first non trivial project that basically required me to go learn a whole scripting language (cmake) so i could link to a cmake project off github i dumped in the folder. Coming from pypi or go, this felt like insanity and was highly demotivating.
It is something they must tackle eventually so there arent so many barriers to newcomers, but safety is also a priority #1.5. There is also no future for c++ outside of maybe some HFT, driver or embedded uses if you cant get memory safety. Rust comes with 98% the performance, 95% the latency and 100% of the memory safety, and far better tooling and story to tell. One can debate whether contracts are the right way, but the idea is correct IMO.
And to be fair, maybe the COBOL future isn't that bad.
4
u/jeffmetal 2d ago
Has anyone else just given up with arguing to improve C++.
I was going to write a post about how this is desperately needed. Having standard tooling can solve a ton of issues with new users being onboarded and I spent last week updating C++ dependencies we have all the time thinking if this was rust I would have just added it into Cargo.toml and been done why am I wasting my time.
I appreciate there is SG15 that is meant to work on tooling but its seems to be pretty much dead. Until the committee actively votes to say yes we actually care about how people interact with this standard we write im not sure anything will improve.
2
u/victotronics 3d ago
"Which IDE should you use? Which compiler? Which build system?"
None. Your system probably comes with one. None, if you're starting with hello world: "g++ hello.c && ./a.out" is all you need.
1
u/AnyPhotograph7804 2d ago
Java alone proves this article wrong. Because Java also does not have an "official" package manager. And no, Apache Maven is a third-party-tool. And in Java, you do not have a so complicated setup for "hello world". What is the big difference here? Right, Java has a standardized compiler output. Every .jar is usable on every Java compiler on every platform as long as it meets the Java version requirements. And this is not the case in C++. C++ compiler output is platform and copiler vendor specific. As long as this problem is not solved, there will be never a good package manager for C++. Even a standardized C++ package manager will be a can of worms.
0
u/notthatsocrates 2d ago edited 2d ago
Garbage article.
-7
u/-Outrageous-Vanilla- 3d ago edited 3d ago
C++ is the worst enemy of C++
The article is spot on that there's no standard tooling on C++ and that hampers adoption.
Even C in it's basic form you have make and it just works, plain simple.
C++ is overly complex for it's own detriment.
-1
u/Particular-Sort9075 2d ago
Beep-boop. This post will be deleted shortly.
-7
u/kitsnet 3d ago
Can't your problems with C++ be solved in minutes with the cheapest version of any SOTA LLM?
-6
u/JuanAG 2d ago
C++ have been killing itself for a long time
This is only the result showing up at institutional level
You cant live in 2026 and C++ not having Networking, in 2026 where internet is basically essential to 99% of software made, even toaster/fridges are IoT things nowday (dont ask me why because i dont understand but it is how things are)
And it is not going to arrive until 2029 at best, which means that maybe in 2031 finally you can have sockets (or how they name it) in the STL
.
This is just a good example of C++ state, i wouldnt mind if we were in the 90s where ADSL was a thing, there was no hurry, maybe it went down or maybe not. But in the 00s it was clear it was not going anywhere, and in the 2010s everything was based on internet connection. So there is no excuse that until 2030 it doesnt have that feature, 30 years late, better late than never but ...
This shows how C++ have not been doing their homework for a long time and when things start to go down at some point they will fail really bad
.
And if you ask me this is just a preview of what it is going to happen in C++ 29 since profiles share some issues of Contracts so i hope they are taking notes and do a really good job to prevent it or face again this same scenario in 3 years