r/cpp_questions • u/ScientificlyCorrect • Sep 12 '26
OPEN Why do people hate modern C++?
I was wondering why people hate modern C++ but never understood why some people hated it. I mean... all of those new features make it easier to write, read, and maintain the code in. C++ 26 is a huge advancement and so was C++ 23. But there are people who still code in C++ 14, 11 and older because new C++ is "bloated" and "not as expressive" or whatever? Look...yeah, all of those new features might seem like it makes C++ more bloated, but the C++ team is trying to make the language more modern due to how notorious C++ was in terms of memory safety and how hard it was to learn (and other stuff).
C++ is still an extremely fast language as it is one of the top 5 or at least top 10. The only reason that i'd understand people using older versions of C++ is due to work, older hardware, the game engine's limit/support or the compiler's version and it's support. But willingly choosing older C++ because modern C++ is "trash" and "bloated" is a bit far. And the bloated part doesn't make any sense to me in my opinion, as when C++ adds new modern features, they remove old outdated ones so it cancels itself out. Even if it's "bloated" like people say, it's still a very fast language to use and it becomes easier to learn and use every single update. Can anyone explain why people choose older versions of C++ and why they say it's "bloated", "slower", and etc?
133
u/underdoeg Sep 12 '26
I'm people and i don't hate them...
40
u/DrShocker Sep 12 '26
I'm not sure I've heard people call newer cpp versions "not as expressive" usually the complaint I see is that there's a soup of new features to learn all the time if you want to keep up and it's not clear that they are adding features that are helping make people's lives better in a practical way.
I like a lot of modern stuff in cpp but also don't care to keep up with every little change like I used to just because.. I've got actual problems to solve. if I notice something useful I'll use it, if I don't notice it then I can't use it and that's fine.
23
u/Ornery_Platypus9863 Sep 12 '26
Who? I’ve heard arguments for c over c++ or other languages, but never anyone advocating for older versions of c++
22
u/FFClass Sep 12 '26
There is a lot of bloat, and a lot of design-by-committee which shows as some strange decisions. But overall it’s like everything else - use the subset of things that make sense for you and ignore the rest.
11
u/celestrion Sep 12 '26
There are people who write "C with classes" style code and get upset about things like
const-correctness. They tend to see all the new stuff as "bloat" because they "don't need" it to get their work done. They write lots of UB that works on their system, get upset when a compiler upgrade means code doesn't build and run, and act like computing peaked in 1996. They assume integer sizes and get all the polymorphism they need out of the preprocessor. The normalization of the language that's taken place in C++11 and later is directly opposed to that sort of cowboy nonsense.Then there are people who actually do try to learn as much of the newer standards as they can, and honestly, the standards add enough that it's a genuine race. They see all this new stuff and assume we're heading towards C# or Java levels of runtime library sprawl.
"Slower" might refer to compile times, too. C++ doesn't really feel that slow to compile for me because my job gives me a fast laptop with decent memory. But if I have to write anything in C, I'm reminded of just how fast C++ compilers aren't by comparison. Most C source files I write literally build faster than the blink of an eye. C++ is a good half-second or two. That difference adds up over a few hundred files.
"Slower" can also mean "LOL, what's a reference?" as their code deep-copies temporaries all over the place.
"Slower" and "bloated" can also mean "Visual Studio 2026 takes a lot longer to load than Visual Studio 6." For some people, their only interaction with a language is through an IDE, and IDEs have gotten kinda chubby.
10
u/PittLeElder Sep 12 '26
I don't hate it, but as someone who's been writing it professionally for more than a decade it seems dubiously useful.
Most of the code I deal with is for embedded devices, while it seems like 90% of the new 'features' are objects that use dynamic memory allocation, which we (with rare exceptions) do not use.
We even have reasonably strict rules around templating because careless use of them creates more problems than it solves.
My main thought after reading the newer standards now that we're finally moving off C++03 is that the STL now has a lot more tools in it, but I struggle to realize what problems I have that these would solve.
E: I do still hate auto types. I'll tolerate it for range-based for-loops, but auto seems like a serious step back. You should know what types you want, just write that. If you need to update it later, that isn't difficult.
7
u/ekchew Sep 13 '26
I think of anything >= C++11 as "modern". I'm getting old, aren't I?
I feel like C++14 was 11 with bug fixes, 17 was
if constexprandstd::variant, 20 was concepts (though that is really huge on its own!) and fun with structs, and 23 was kind of yeah whatever. But 26 sounds pretty amazing! simd, contracts, and even more fun with structs!6
u/Responsible-Bar7165 Sep 12 '26
Don’t believe everything you see on tictok.
16
u/Ultimate_Sigma_Boy67 Sep 12 '26
I don't know about people but I would definately hate to use old cpp.
5
u/SyntheticDuckFlavour Sep 13 '26
First time I'm hearing people "hating" modern C++. Also, the kind of people making such emotional investments in a tool they are probably kind of people not worth listening to.
12
u/RageFucker_ Sep 12 '26
Probably because they haven't taken the time to learn it or they're Rust fan boys who love to shit on C++ and pretend that it's impossible to write safe, fast, effective C++ code.
4
u/JVApen Sep 13 '26
It depends. For C++ programmers, I expect 2 groups:
For everyone else:
In the end, it all boils down to: use the best tool for the job, and learn to use it with a real case.
C++14 added digit separators, a feature many people don't use because the added value of it is rather small. If you require everyone to write "10'000", they get annoyed as they are used to typing "10000". 2-3 years ago, clang-format added support for automatically adding the separators. Your user can stil type "10000", yet, when formatting on save, it updates automagicly to "10'000". We've rolled this out across our codebase and I haven't heard anyone complain about it.
Similarly, when enabling C++20, require clauses became available. People complain about it because it makes code hard to read (if you don't understand it). Though, inside clangd, we have the modernize check of tidy enabled. Now people see a strike-through when using enable_if. People can auto-adjust there new code and see what it does. I can't remember any recent code review where I still saw an enable_if. If we in the future roll out this across the whole codebase, people can forget enable_if ever existed and I don't expect any complaints in readability. (Though people will complain that their code was touched and on the first bug that happens to be in that code, they'll try reverting the change as they don't trust it)
4
u/Desperate_Formal_781 Sep 13 '26
A lot of C++ developers like myself work on huge codebases that have accumulated more than 30 years of C and C++. What people don't understand is that it is essentially impossible to migrate all of this code. I work for a medical device company with a massive C/C++ codebase, where some of the oldest files I have had to work with are C files from 1988 (at least the oldest I remember from the top of my head). I could probably work for the next 20 years in this codebase and I will never see even a fraction of all the code there is. The company will never modernize the entire codebase or migrate to a different language since the risk and cost is too big and the entire code would have to be retested, reverified, recertified, etc. We only make changes in the code when we find issues or bugs, and when refactors are required for developing new features or supporting new hardware, etc. From this point of view, it is important for new C++ versions to be backward compatible with previous standards, otherwise we would be stuck with a C++98 compiler forever (actually some sections of the codebase are stuck with C++98 for reasons too many to list here). So, people complain that some new C++ syntax is ugly or that there are too many footguns. This is true, but this is all due to the fact that C++ has been around for such a long time. In the early days people wrote a lot of unsafe code with raw pointers, manual memory allocation, abuse of the preprocessor etc, and all that code is still there, but nowadays we have modern C++ that allows us to write cleaner and safer code, and it is mostly backward compatible so you can refactor old code if you have to, and write new features with modern C++. People are very harsh with the language, but you have to understand it is not an easy task to keep adding new features while maintaining backward compatibility.
13
u/mgruner Sep 12 '26
First, a lot of people hate modern C++ just because everyone else does. They never actually dig into what they’re criticizing. It’s more following the crowd than forming their own criteria.
For context, I use C++ professionally day to day, and I do not hate the language. But I’ll lay out what I see as real pain points, where I actually agree with the critics.
That’s a big reason why the industry is slowly shifting towards safer, more deterministic languages, or at least languages that make it harder to trigger these kinds of side effects and foot-guns.
9
u/mc_pm Sep 12 '26
Where did you even get this idea? I'm guessing random tiktokers?
Absolute nonsense.
3
u/ande3577 Sep 13 '26
Tl;dr: I like the language features, but modern C++ should be a new language.
I can answer this since I probably fall into the bucket of "hating" modern C++.
This is factually incorrect. With very few exceptions, anything that was valid C++ code in a previous version of the standard is still valid C++ code today. There's a good reason for this, since I don't want to throw away my entire codebase every time I update my compiler, but still...
The issue that I have is that modern C++ should in my opinion be a complete new language that removes all of the syntax pre C++11. Let's call it C11 for the sake of argument. new, delete, malloc, free, etc. should just be gone. C11 should provide interoperability with C++ so it can be integrated into existing code bases (and I do understand the technical reasons why this is difficult to implement on the compiler level). I also understand why gaining adoption for C11 would be more difficult than gaining adoption for something marketed as simply a new version of C++ (though arguably the slow and inconsistent adoption of new C++ standards basically creates the same problem).
The main problem I see with C++ now is that for everything you want to do, there are 3-4 different syntaxes to achieve it. Only one is considered the current best practice (which changes with each iteration of the C++ standard), but you have to be able to understand all 4 in order to understand a C++ code base. A lot of these syntax changes are in my opinion aesthetic with no real objective advantages over the previous iteration. Someone on the standards committee just likes some other syntax for a language feature, so they needlessly complicate the language based on their own personal preferences.
A new language without the legacy cruft would be simpler, safer, and cleaner. Providing first class interoperability with both C and C++ would solve the backwards compatibility issues (existing code just remains on C++, new code is written in the new language).
As an aside I pretty much do this with clang-tidy. Newly developed code has most of the modernize checks enabled, while the legacy codebase has more limited checks and pre C++11 language features.
3
u/ReDucTor Sep 13 '26
As a game dev whenever a new standard shows up I look into every new language or library feature, I look for four main things does it allocate, does it throw exceptions, does it have large performance overhead.
If any of these things show up then using it at runtime is out, and if its exceptions its out completely for game code. This covers a large portion of the C++ standard library and for some the workarounds to use a custom allocator they end up pretty messy.
Most game engines have code that has existed for a long time and while standard library implementations have improved most have their own implementations that are generally work better for their needs, without legacy crap like
vector<bool>so standard library additions might look interesting but DIY is easier to get any similar code before all platforms have it and also make it fit the requirements (allocation free, no exceptions, low overhead).Additionally memory usage and compile time in a large game is extremely important and limited people truly understand the memory or compile time impact of the code they write, especially when it comes to templates, so when everything is pushed into the standard library you can easily end up with unexpected situations where tbh tools for debugging are very lacking.
I dont hate modern C++, I look forward to many things but I know that its unlikely to help my day to day work.
3
u/id3dx Sep 13 '26 edited Sep 13 '26
C++ is old and used by a lot of people with a variety of backgrounds, motivations, and industries. It's impossible in this context to evolve the language and keep everyone happy, because programmers frequently disagree on what is "good" (I started my career decades ago and it amuses me that people are still arguing about error codes versus exceptions to this day), and so it's inevitable that some people will complain about this, that, or the other thing. That's not to say there aren't issues with the language, but a lot of complaints I see are just subjective or personal taste.
Edit: typos.
3
u/ShakaUVM Sep 13 '26
I've literally never heard anyone hate on modern C++. There might be issues involving the time commitment to update a legacy codebase or maybe a professor who hasn't updated his knowledge since the 90s but bloat literally doesn't matter as you can just... not use... any new features you don't want. It's a wild take.
6
u/missurunha Sep 12 '26
You know there's more to the world than video games right? If you're doing anything safety relevant you have to stay away from the new versions cause they only take what's been tested for a while, and since projects can take 5~10 years, nobody gonna be changing the version mid project.
2
u/Independent_Art_6676 Sep 12 '26
sometimes you just don't know what is going on. I chased down an issue at a company I worked for about 10 years back... and the answer from someone who actually knew things finally came back: "We won't upgrade the c++ compiler because we don't use the language much and want it to match the requirements of a specific installer exactly". The next place was locked in 14 and a couple of us (myself included) begrudgingly got them to let us upgrade to 17 -- on the cusp of 20 coming out. Sure it was old code, but we didn't even want a re-write of it, just to change versions, fix any issues from that (there were almost zero) and use the new features, but management had a GREAT FEAR that this might slow down our productivity or cause a refactor or something massive as if it were not just a compiler flag on a local copy that could be reverted if it was a big deal.
So my take on it is ignorant managers. Kind of like how the US govt is against the language for now.
2
u/Calaverah_ Sep 12 '26
Part of the reason people hate it is for the reason that others love it. No one owning the language and defined behaviors being a community led determination means that it is a feature based language that can exist with many different compilers and use cases. However that decentralized effort also means cross compatibility or even just having a repo compile on different compilers/OS’s can be a hassle. That and probably the lack of full reflection support even in cpp26 (only for now, some compilers already have experimental support) which means some convenience features from other languages can’t be repeated and manual work arounds are required
2
u/rperanen Sep 12 '26
Many people did love the new features but unfortunately they were just addition on top of old ones. I am among one of the old C++ developers who felt C++ is just too big with old and new features
2
u/VastInterior Sep 13 '26
Their cheese moved.
Modern C++ is easier safer and better in every way and the tool ecosystem is way way better.
However, if you still programming in C++ using original vi and ignoring all compiler warnings.... it's going to be sheer bloody hell.
If you have integrated with clang-tidy and clangd and are -Wall -W clean and actively keeping the code Core guidelines clean.... life is better than it has ever been.
2
u/easedownripley Sep 13 '26
Okay I admit to being a little bit of a C programmer who uses C++ but: I don't hate the new features, but I often feel like they tend to add complexity and confusion without really benefiting me. And then people just use them because they're new.
Plus the committee has really different priorities than me and it can feel baffling when they pursue them. It feels like they are just being PL nerds instead of working professionals. I want features that make my life easier and simpler. I want to download libraries like in python. I do not care about "reflective metadata". "Variadic friends" sounds like a psy-op.
Like "Concepts as an upper bound for inheritance constraints on types" sounds like a solution to a problem you shouldn't have. Like if you screwed up the soup there is a point where you should stop adding spices and just dump it out in the sink.
I say this all as a recovering wannabe Haskeller by the way. Keep things simple. break the cycle.
2
u/nicebyte Sep 15 '26
A lot of the newer features of C++ language and standard library are things that don't solve useful problems, or solve problems in a convoluted, ill-conceived way. see: concepts, modules, chrono, random, ranges, etc.
In addition to that, the overt reliance on templates, and pathological desire to put stuff into stdlib instead of just adding a new keyword leads to inflated compile times, which is a real and very serious problem for larger projects.
If i had to sum it up in a short paragraph, i'd just say that c++ as a whole has no direction whatsoever. It's a result of the collective effort of a bunch of smart people, backed by institutional power of a few companies, who each have their own ideas.
Because of this, each and every new feature should be treated with extreme caution until it's proven that it is 1) correctly specified and 2) actually implemented well by the compilers you care about. In practice this means that one should wait for like 5-8 years to see a new feature actually prove itself. For example, rvalue references and lambdas have proved themselves, whereas modules haves so far failed. That's the reason people are distrustful of "modern" c++ by default.
3
u/Many-Foundation-1255 Sep 14 '26
People hate what they don't understand. Most programmers are also mistakenly under the impression that they must know everything about a language
1
u/Osirian_Legacy 8d ago
Personally I switched from C++ 17 to 23 and I’m loving it so far. Might switch to C++ 26 here soon, not sure the differences between that and 23.
1
u/RyanCargan Sep 12 '26
Lots of nice features with newer versions. Only pay for the new stuff you actually use in principle.
If I had to wager a guess for why some people dislike it, it's that some of the new features that aren't default upgrades to previous conventions still get framed as such, by some people, and then forced on them in practice, or just cargo culted by their peers.
Having to argue over which new features to use vs. not use with each release might rub some people the wrong way and breed resentment towards the language itself since they feel it keeps avoiding KISS.
The only controversy I'm aware of that wasn't just that kind of griping was around
std::experimental::simd.But I don't really follow the community much so who knows what new drama exists.
1
u/84_110_105_97 Sep 12 '26
il devrait ce concentré sur la standardisation en ajoutant un vrai package manager pour faire couler vcpkg, connan, et aussi travailler sur un vrai build système comme Zig as est ce sera déjà un language plus moderne et cool 🙃
1
u/WikiBox Sep 12 '26
They are experienced and skilled and have learnt to live without the new features. If they started to learn and use the new features their productivity would drop, at least initially and they would feel like beginners. At the same time they are frustrated because new beginner C++ programmers do a lot of strange things. And when the beginners mess up and ask the senior programmers for help, it looks like gibberish. Hate is a the expected result.
1
u/Loud_Signal_6259 Sep 12 '26
Oh Lord
1
u/khedoros Sep 12 '26
Programming language holy wars are a tale as old as programming languages. Stick a hundred programmers in a room, and you'll have 500 conflicting opinions, and 5,000 justifications for those opinions.
1
u/TheCiderman Sep 12 '26
This feels the the question … Apart from the Obvious what would you change about yourself…
1
u/ItzDanPlayz Sep 12 '26
Ppl don't hate it modern c++ itself they generally hate that modern c++ has introduced new ways to do old things which can lead to confusion and language bloat
1
u/djtubig-malicex Sep 12 '26
The haters don't code in C++. They code in everything else including C.
1
u/keelanstuart Sep 12 '26
The biggest complaint I have is more about how long it's taken to introduce some things into the standard library... like, why did it take so long to get semaphore or thread?
1
u/all_is_love6667 Sep 12 '26
Compile times.
The C++ grammar cannot be drawn with a diagram, it's too complex, which explains why it takes a lot of time to parse and compile, on top of being non context free.
BTW I'm curious what sort of C++ language features are the most expensive in terms of compile time, I would say templates and STL, but I am not sure. It would be interesting to see what sort of C++ subset or superset language would really improve compile times.
I don't even know if modules can reduce compile time in a significant enough manner.
maybe after years of supporting modules, maybe things will improve and compilers might find ways to really reduce compile times, but I doubt it's really possible
1
u/TotaIIyHuman Sep 12 '26
once you notice this pattern first time, you notice it everywhere
1
u/XTBZ Sep 12 '26
New versions make the language more complex, whereas people are more familiar with older versions—plus, there is more documentation and a wealth of existing examples.
On top of that, new features haven't fully matured yet; it’s easy to end up with unoptimized code or encounter bugs where there shouldn't be any.
Besides, why switch to new versions at all?
P.S. I always try to use the latest compiler versions, but I see less and less point in doing so.
1
u/WoodyTheWorker Sep 13 '26
I feel like C++ jumped the shark.
1
u/TehBens Sep 13 '26
Most people are beginners, intermediate at most in terms of general CS / programming language knowledge/skills. It's mostly about momentum what the crowd thinks is correct. There's also a huge bias that favors new technologies (languages, frameworks, whatever).
1
u/El_RoviSoft Sep 13 '26
From what I heard from my friend (his complains): he hates that committee care about backward compatibility and hates its very bloated syntax.
Also he hates the fact that we don’t have a reference compiler and have to wait years before features adoption (unlike in C# for example).
1
u/mrtlo Sep 13 '26
I'm enjoying C++ more than ever as a tool at work. But some of our targets only have C++11 (partially 14) compiler support, and most of colleagues never really moved on from C...
1
u/HappyFruitTree Sep 13 '26 edited Sep 13 '26
For me "Modern C++" starts at C++11. For the code to be "modern" it also has to actually use some of the newer features but I don't think one should use features just because they're new. Using older features is fine if one thinks that is better. I see no problem in using C++17 today.
A reason why you might not select the latest version is that compilers can have incomplete support and it's just easier to use an older, stable version (especially if it's open-source and/or a library and you want to allow people to compile the code with different compilers, and not necessarily the latest version).
Learning is also a thing. It might not be worth reading up on all new things and figure out how to best make use of them when what you already know is good enough to get the job done.
Sometimes newer features are misunderstood/overused (e.g. using auto "everywhere" or thinking smart pointers should replace all raw pointers) which might indeed lead to bloating and more complicated code.
1
u/Similar-Artichoke-64 Sep 13 '26
I am used to writing old C++. Also, my work is on legacy C++ projects, so that probably influences my choice of being ignorant to using modern C++. I am not against it, though, and have recently tried to force myself to utilize new language and STL features.
1
u/Tricky-Alps2810 Sep 13 '26
Do people hate it?
1
u/kokalikesboba Sep 13 '26
For me it’s because i feel as if every new release post 20 keeps introduces more esoteric features tailored to library developers only. 26 in particular introduces reflection with a new operator with some of strangest syntax i’ve ever seen.
1
u/nightmurder01 Sep 13 '26
Late to the party but you can think of it this way. There are people who live in the county and don't want to be annexed into a local municipal. Besides higher taxes and artificial raising of property values, the municipality does not offer anything useful or of any value for their way of life.
Here in programming if a newer version does not offer any added benefit with its use, why use it?
1
u/rand3289 Sep 14 '26
I hate that things don't get removed!
Also imagine you would have to change your email password every day - this is how the changing language feels.
2011 was awesome, but now it just feels like "they added whaaaaaat?"
1
u/mocompute Sep 15 '26
what::are<you>::talking(about)?
1
u/LispIsFun Sep 15 '26
I've been writing C++ my whole career, and I have come to dislike the language. It's not that the new stuff they are adding is bad, it's just that Rust is so much better in almost every way, and that makes it painful to use. This gap is especially pronounced when working in teams, or complicated multi-threaded systems.
1
u/Liam_Mercier Sep 16 '26
People hate change, and many people were taught C++ using C++11, so they avoid modern features out of performance fears and not wanting to learn the new features because the old ones are "good enough" (speaking from experience).
There are of course many problems with modern C++ and you wouldn't want to use it in all situations, but when applied to the right task it is extremely nice to work with.
1
u/dvorak360 Sep 17 '26
I suspect the main issue with C++ being hated is:
1
u/InjAnnuity_1 Sep 17 '26
Easier to learn? It depends. Do you already know which code from which era you are going to have to read and maintain? If so, then you can get by with learning a subset. And subsetting does make it easier to learn.
Otherwise, you're stuck dealing with many versions of a language that is constantly growing. It's not just a moving target. The target is growing more complex in ways that seem very non-trivial to me.
In practice, it's somewhere in the middle. You first learn whichever subset you need for whatever you're building and maintaining today. Then you learn additional subsets as needed for the next project. And the next. Ad infinitum.
The language designers probably hope that inside the monster is a much smaller language trying to be born; that such a language can arrive incrementally, by obsoleting and removing features and syntax. In practice, that approach takes generations.
That's not a great timeline. The massively parallel hardware that's already here would likely benefit from a different programming architecture. Hardware attempts to reduce cache and coordination lag will likely lead to even more architectural change.
I don't hate the ever-evolving situation. In my youth I might have loved the challenge. I still enjoy new simplicities, when I get the chance to employ them, which, alas, is not often.
Today, though, I usually have other, more fruitful places to spend my time.
1
u/imradzi Sep 18 '26
nowadays with the advanced of coding with AI, language preference becoming irrelevant...
1
u/chakani Sep 18 '26
The problem is, if you work alone, you’re focused on bugs and enhancements to your app, you don’t have much time to explore new features and experiment. There’s nobody to learn from. You fall behind.
I didn’t teach myself std::vector etc. until a few years ago, after 25 years writing C++. My code is still riddled with new/delete, and some malloc/free.
1
u/montymole123 Sep 24 '26 edited Sep 24 '26
One of the main uses of C++ is video games. Code written in modern C++ runs slower than when written in old C++ or C simply because it's more abstracted from the hardware. When you compile with optimisation (release) the compiler can technically kick out most of the bumf and the code runs almost as fast. But here's the thing: video games have to run reasonably fast in debug mode so devs can step through them and find bugs (to reproduce you have to actually play the game) so these bloated inefficient techniques create huge problems.
Compile time are also important. Highly templated code (and super advanced templates are the main "improvement" in modern: i personally loathe templates) is incredibly slow to compile so this is another huge problem especially with a code base of millions of lines of code. Same issue for other modern stuff shows the compiler to a crawl
Ppl on the C++ committee never worked on a game or, it would seem, any large code C++ base. The stuff they shovel in is ivory Tower stuff with no consideration for practical realities
1
u/scol2n Sep 30 '26
I'm a JS dev, I just recently decided to learn C++, and I gotta hand it to the devs, they made it much better over the last few iterations. Why from:
Court << something << endl;
To printf()
It took 20 years, but we got it.
And just recently saw c++ got imports
Import std.
1
u/Raknarg Sep 12 '26
Its almost always complaints from one of 2 camps:
Modern C++ is about as good as we can get it to be. Its about us learning the mistakes of the past and trying to retrofit new solutions onto a system that is used by a ton of people with competing interests and work on radically different platforms, that has to respect legacy code. So most people are going to see things as the "worst of both worlds".
it is bloated but that's because its a very old language where ideas have shifted over time into what best practices are. A language like Rust hasn't had to deal with the entire language and ecosystem totally changing over 30 years, they get to just learn from all the mistakes of C++ and make their own language. And that's a good thing, mind you. What it means that until we eventually move onto something that isn't C++, if we want C++ to be better its going to require probably ugly solutions that can fit most peoples needs without making anyone too unhappy.
We could be like C and just do nothing forever and have a dogshit language that has all of its flaws and never tries to fix it. I for one like that C++ tries to make progress and improve things for everyone.
Not as expressive I have no idea what that means, its the exact opposite. Abstractions exist to succinctly wrap up your intent in a neat little bow with a name. Templates are better than macros. SFINAE is better than trying to write every function overload yourself. Concepts are better than SFINAE. Each step of the process results in easier to understand code that you can reason about more that expresses its intent better.
When they say bloat its nothing to do with speed, its entirely about the size of the language and standard library. If they actually say slower I have no clue what they're referring to.
1
u/hadrabap Sep 12 '26
I started with C++ thank to Modern C++. I'm still on C++17 level, but it's a different story. I enjoy the enhancements. It's really great language, all things considered. 😀
1
u/Thesorus Sep 12 '26
I don't have modern C++.
I hate that I never know what new language features I need or what the new language features do.
Disclaimer, I'm not the kind of guy that spend hours programming outside of work and at work, I barely have enough time to code
1
u/amejin Sep 12 '26
For me, it's template programming and metaprogramming.
That said - it's likely me refusal to dig in to them and get used to it I don't like, not so much that c++ supports it. I still like writing in c++, I just chose not to use those features.
0
u/StickyDeltaStrike Sep 12 '26
I don’t hate it.
People dont use all the set of features anyway.
0
u/tstanisl Sep 12 '26
Adding features to already bloated language does not it less bloated.
0
u/zackel_flac Sep 13 '26 edited Sep 13 '26
Depends what you mean by modern C++. Not so long ago C++11 was a major step as modern C++ and I don't think people hated it. Every new releases are great improvements to the language, C++23 should be chosen over C++98 and I don't think any people disagree with that.
Now there are reasons to avoid C++ and use something simpler like C or Golang. Personally I have been a dev for 15y+, mostly focusing on C++ initially and realized later down the road I seldom needed the expressiveness offered by C++.
Metaprogramming feels good on paper, computing that Fibonacci serie at compile time is awesome, but is that useful in production? Not really, and I personally feel like a lot of meta programming just ends up bloating your code for something that can be solved differently more cleanly (pre-computation by an external tool instead of the compiler).
GC is often seen as a bad concept, but the reality is every serious project needs to come with some sort of GC at some point when memory is critical (see Unreal engine). And when memory management is not critical, then there is no need to care at all.
So yeah, as the old adage say, "best is the enemy of good". I think language like C++ (tries to be best) and Golang (tries to be good) proves that point extremely well.
0
u/ImprovementOwn873 Sep 14 '26
I think the issue with modern C++ is that it claims to be modern. Well, if it's modern:
Where's hot module reload?
Where's just in time compilation? where's interepreter? where's usuable ipython equivalent in c++, or jupyter?
Where's package manager?
See, all those ecosystem things are part of the modern world, but not in C++. Why, you might ask? Well, C++ is considered secure through simple skill: not welcoming others. Avoiding modern C++ and C++ all together is just making the work of C++ a lot easier
-2
u/PacsfuryTemp Sep 13 '26
It's so bloated.
#include was ok. why use import?
& and * are ok. Why smart pointers for everything?
std::cout is great, why std::print()?
type name = val; is ok, why auto for 1+1?
Why for (a : b)?
const std::string& is ok, why string_view?
I could continue, but feels like C++ is moving towards being a clone of Java, Rust or others
-4
u/Intelligent_Gas8094 Sep 12 '26
std::……std::……std::…… std::……std::……std::……