[pjmlp]

The problem isn't C++, the problem is that the meagre resources those teams have available, rather spend their time catching up to ISO C and ISO C++, than improving error messages.

Hence why SARIF has seen big adoption, as they hope that by exposing that , there are others ways to have others have tools that process SARIF.

[vlovich123]

C++ has way more resources than almost any other language. There are or were teams from Microsoft, Google, Apple, and Bloomberg who work on the compiler. Lots and lots of man hours have been spent and I’d say wasted. The problem is C++ the ISO committee and that is the language essentially.

They had a chance in c++11 - we’re going to make a modern c++ that fixes the old problems. And for a time that was true. But they’ve completely lost their way again and getting caught flat footed when the US government recommended people stop using c++ and instead of figuring out how to fix the language they doubled down on unworkable ideas that don’t meaningfully improve the situation.

I think the advice will be to run fil-c in production and then c++ will have an issue as to just what it’s identity is because in practice it will be significantly slower than alternative approaches.

[pjmlp]

Most of the companies that you named, nowadays don't care about C++ as much as you think.

The work in clang and GCC is mostly done by volunteers, big names like Apple and Google rather focus on LLVM itself for their languages.

Microsoft seems to have layed off quite a few people, and is mostly focused on keeping it going for existing projects, in the context of games, as second language paired with .NET, CPython and JavaScript runtimes.

The last framework they published (C++/WinRT), its baseline is C++17, with no plans to upgrade it.

They just released an updated memory model for C# for low level coding that should be competitive with Swift and Rust unsafe models.