If I remember correctly some discussions on /r/cpp.
As for Apple, OP is right, Metal Shaders are based on C++14 dialect, IOKit/DriverKit use an Embedded C++ dialect, and for everything else there is Objective-C/Swift, and they only need enough C++ to use LLVM to develop them.
Frankly, Google should fork C++ and create a new language without the warts and a new standard library.
That's how we got golang.
Another example of this shift would be that Bitcoin’s reference impl (2009) is written in C++, whereas Ethereum’s reference impl (2015) is written in Go.
Go has more mindshare outside Google than on Google's critical infrastructure.
I meant a language by removing all the warts, not removing all the features. :)
Seriously, if Go offered manual/arena memory management and real generic programming - stuff like template template parameters, STL algorithms, auto-vectorization, etc - it could effectively replace C++.
- A post about a C++ ABI break being voted against: https://cor3ntin.github.io/posts/abi/
I would not be surprised if google (or others in favor of breaking the ABI for the c++ standard library) would refocus on their alternate non-std std-replacement-ish library implementations (like abseil) instead given the lack of willingness to fix things in std proper from the committee.