I don't have the professional experience that most of the commenters here have, but I hear a lot of negativity. Like, a lot. Sure, the compilers might be a lit

I don't have the professional experience that most of the commenters here have, but I hear a lot of negativity. Like, a lot. Sure, the compilers might be a little bit behind, but who cares, I believe it's just a matter of time before they implement the missing features. They are pretty solid, the libs are battle tested, the ecosystem is huge (which can be an issue too). For me the bigges issues are: - lots of pre-11 docs and blogs showing up in the first 1-2 search pages - not clear answers or FAQs about how to develop cross platform code (and backward compatible), the devil is always in the details here. - not always clear which tool to use: what do I use for unit tests? And coverage? I would like to have like 2-3 top used libs, the rest I don't care - some things which should be basic in 2022 can be daunting for people coming from simpler languages like Python or Javs, stupid example: dates. I see that with c++20 they did a lot of good work (with chrono, not sure if there is anything else), but that's not enough. The API is really good, but it's quite minimalistic for a 2020 standard. You can clearly live with that, but if you want to keep the language competitive you need to provide also higher level constructs. (Just to say some BS: Take Python's date module and copy it as is.) Finally, if you exclude all the features you won't probably ever use, focus on simplicity and use the tools at your disposal (clang-tidy, clang-format, etc.) I think things are quite OK. But hey, I am not paid to work on old c++ codebases so of course I might be biased :)