On my case, if the language is not part of the SDK, usually it no use discussing its use with the customers.
At least C++ is way safer than C, if one cares to use its features.
Thats the issue with offering an alternative to C++, its not enough to offer a better design language you also need to replace countless of C++ libraries that very capable , mature and very well established. Hence why there is no true C++ replacement out there beyond Java.
Delphi was awesome in countless diffirent ways but just lacked the library support to make it as popular. But at the time was as popular as python is nowdays with around 1 million developers and Borland C++ had 2 million. However at the same time VB had around 6 million and Visual C++ much more than that.
C++ is way safer than C but also way more complex. Which comes as no surprise why C is the go to choice for small libraries. Frankly I rather go C++ as well.
So where we get to use to still use C++?
Interfacing with hardware, COM libraries, JVM/CLR agents and lately portable native code across mobile OSes.
Someday using Rust, D, Go, Swift will be an welcome option, but they aren't there yet, at least for the type of customers we work with.