Your developers probably never had to deliver industrial systems where a bug requiring a update can kill a product line and maybe your company. Runtime is way too late to discover a programming error, the lack of static type checking removes one of the handiest tools for preventing those. --- I spent a month trying to get python to do the things that are easy to do in C++ and was never satisfied with any of it. Tuples are great, everything else was toy-like or was beyond proving correct. --- Once upon a time microsoft basic did not have syntax for declaring variables. A large program I was coerced into writing in MSBasic had some weird non-reproducible behavior. When MS finally added declaration syntax I declared all my variables and discovered some misspelled names, which were the source of those non-reproducible bugs. ---- If python adopted *optional* static type declarations it would be vastly superior to what it presently is. In the meantime all of its good novel features have been ported to C++ via libraries, which shows how vastly more capable C++ is. --- As per someone else's comment, when you realize you've made an architectural mistake you have to laboriously places that might be affected by it, where in a statically typed and declaration heavy language like C++ there are easy reliable tools to do a comprehensive "where used"/ --- And then there is the awful programming advice such as "prefer large flat classes over deeply structured ones". That is farking insane, one ends up using naming conventions to indicate structure instead of using structure to indicate structure. I can see that the poor performance of nested structure in Python makes that a performance issue, but that is something that should be apologized about rather than lauded. ((slash dot is removing the whitespace I used to indicate separate thoughts, apparently their engineers aren't Python fans}).

(Early 1990's anecdote:) C++ was not fully compatible due to stricter type checking and namespace rules. I found the differences beneficial and made my crew use C++ just as a stricter C. We only used polymorphism when it looked like it would simplify the if-then-else implementations otherwise needed.

As a software manager I (with some reluctance) switched to spaces-only as each engineer had their own preferred editors and some did not handle tabs well. Dealing with 3 or 4 people editing the same files became much easier after that. Kinda like Python, its crappy but if it is what it takes to get people working together then it has some merit.

I worked with a technician who said he worked at the site and the capsule door had been red-tagged as not safe, and that Grissom ripped the tag off and had the test proceed. -- My father was a chemical engineer who worked on the capsule heat shield. For the post-mortem he and coworkers were supposed to turn over project notes. In those notes were comments on bad placement of the oxygen lines. They tried to snow under the investigators with piles of irrelevant notes but were questioned within days about the oxygen line.