>Google invented yet another programming language, [...] just to gain access to features that are probably coming down the pipe in C++ in due time anyway. That

>Google invented yet another programming language, [...] just to gain access to features that are probably coming down the pipe in C++ in due time anyway. That's the opposite of what Google perceives. There is no timetable for a future C++23 or even a later version that will make their experiments with Carbon redundant. Are you already familiar with the Chandler Carruth blog post? https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/difficulties_improving_cpp.md https://github.com/carbon-language/carbon-lang/blob/trunk/do... That post also has a link to the Titus Winters pdf explaining some of the ABI breakage that the committee does not currently want to prioritize. I'm skeptical Carbon will spur industry-wide usage outside of Google's internal work. Nevertheless, their rationale for Carbon is in response to the current committee's position of prioritizing ABI backward compatibility over performance improvements.