Interestingly put, "the Objective-C approach to software quality". There's something in the psychology of a large number of C, Objective-C and C++ programmers that makes them overappreciate execution speed and underappreciate memory safety in particular, but also validation and correctness in general.

One of my goals now is to outline safe ways of using C++ for various projects and I'm not too optimistic. In fact I'm unsure what we'll end up with.

Quite true, hence why I say that the problem is human and not technical.

Those of us that come from Wirth languages always put quality and delivering what the program is expected to do before going crazy with optimizations.

I always got the feel that many in the C communities write code as if they were micro-optimizing every single line, just because.

And those that care about type safe driven programming in C++ usually have background in safer languages.

I don't think Swift has a way to catch all runtime errors that others may have introduced in a reliable way.

Perhaps because it's not a huge problem in iOS apps, but for long running multi-threaded applications this is a problem.