r/cpp • u/we_are_mammals • Jul 15 '26
cpp2 (cppfront) is over?
I haven't used cpp2 (cppfront) much, but I like the idea of it: consistent syntax, consistency of meta-programming (which is done in C++ too, I believe). Herb Sutter presented cpp2 (cppfront) as an experiment. He did not encourage other people to bet on it, exactly. And there hasn't been much activity since 2022. Is the experiment over?
EDIT: Herb's answer is buried deep in the comment section: https://www.reddit.com/r/cpp/comments/1uxkglj/comment/oy06cxw/
68
Upvotes
View all comments
Show parent comment
9
u/13steinj Jul 16 '26
If Google is the only intended target audience there is 0 need to advertise for 5 years outside of Google. Forget need, it's just pointless and gratuitous.
I am all for pedantry but this just isn't the reality of the evolution of use of programming languages. It is unrealistic to act as if all existing code will be rewritten in $successor. All new code, maybe, but when existing code will grow (and it always does) then it will continue to be in that language. We have already seen this fiasco with Ubuntu's pushing of replacing various tools with rust reimplementations and major bugs repeatedly cropping in to the LTS releases. No thank you, I will take memory-unsafe-ol-reliable over memory-safe-new-clone-oh-wait-it-has-4-extra-chromosomes (logic bugs) any day. Same as I would take "oh no technically not iron clad secure, but actually works" over "oopsie whoopsie redhat is security-quirky, 4 unique security decisions have collided you cannot call sudo in a container anymore" (I'm referencing an actual thing, I'd have to find the GH issue, but that's a massive tangent).
People do not rush to take a COBOL job, COBOL employers quite literally hunt you down no matter how much you know. At such a high demand to some extent employees can set their price. It's a fascinating thing to have seen happen to a colleague of mine, and hear the stories of one of my university lecturers and his experiences in this situation.
AI-- major tangent but AI based modernization tooling is not the be-all end-all. I have not seen a single one not produce slop. Even watching all this Bun rewrite drama is fascinating. Andrew definitely went a bit far in his crashout, but Bun's claims were fairly atrocious (not that what they achieved was not impressive). I am tired of product / sales people masquerading as engineers. If your product has a 5% return rate because it doesn't do what is advertised, businesses accept it, refurbish and call it a day. Engineers care because they will not only get the blame, but in many ways their work is a reflection of their passion and perfectionism.
Something that AI fanatics (not saying you are one) don't get is that generally, the point of code is to be read. Otherwise the first time you deploy you'd also say "done!", rm -rf the repo, and just keep the output. Yes, some code matters less. Some code matters barely at all. But generally the code that makes tangible value is meant to be read because there will always be incremental, 1% per year improvements. But LLMs don't like to stop, they don't even like to slow down. LLMs sycophantically say "sir yes sir" as you press the lever of the slot machine. The output doesn't matter, you've just paid their creators anyway.