Earlier quoted context omitted.
I call shenanigans. That's true of simple scripts, I'm sure. But you can't seriously claim to me that you can understand decorator idioms, iterables or list comprehensions without a deep understanding of the language. What you say might have been true for Python c. 1998, it certainly isn't true today. Broadly: reading code is just hard. It's much harder than writing code. There are no non-trivial codebases that can b…
That is a given, I agree. But a complex program written in C++ (or using advanced C++ constructs) will scale much worse than a Python one, in my opinion.
Yesterday I spent a chunk of my day debugging why my Python script reported that zero computers on the network were using DHCP. Apparently the Win32_NetworkAdapterConfiguration property DHCPEnabled returns 'True' or 'False' in Python (those are strings, not bools). In C++ that's a compile time error. The Microsoft documentation says DHCPEnabled is a bool. So between implicit functionality (evaluating strings as bools) and dynamic typing, this isn't screaming scalability to me.
Yes, this is just one example, but it points to a whole class of errors that are lurking out there in production code. My guess would be, a complex C++ program written in the Lakos style would be more scalable than the equivalent Python program.