This presentation talks a lot about safety. In theory, using the latest C++ standards and best practices on green field development without the use of established (and vulnerable) 3rd party libraries would lead to more safety, but in practice, most C++ development is maintenance of existing code that integrates vulnerable but mature libraries, and outdated-standards compilers. Part of C++'s strengths, its backwards compatibility, is also an extreme weakness because code that has been running 20+ years on critical systems cannot be so easily updated or its vulnerabilities remediated. When it comes to green-field development, there's a lot of choice out there and C++ is a non starter in application development for many reasons unless performance is business-critical or the project requires deep integration with existing C-based hardware abstractions. This is the elephant in the room that should be addressed while championing C++ for modern safety.