I believe that it is irresponsible to

1. Start new projects intended for production that have nontrivial security threats in C or C++

2. Not have a plan to categorically prevent memory safety errors in legacy codebases over the next decade or so, whether that be by transitioning to new languages or by applying rigorous hardware-level memory tracking

I bet if liability was a common thing in software delivery, those languages wouldn't be the first option after a couple of lawsuits.

Yeah can you imagine if it actually mattered if companies made choices that they knew were inevitably going to lead to zero-click exploits on internet-enabled devices? Somebody sitting down to write a media decoder in C today knows that this means a steady stream of exploits harming their customers.