Happy Halloween! Google halloween doodle
Our job is to solve problems, not spoonfeed compilers, so we like dynamic languages that adapt to us, without arbitrary, rigid rules. We need clarity so we can communicate using our code. We value conciseness and the ability to express a requirement in code accurately and efficiently. The less code we write, the less that can go wrong. (And our wrists and fingers are thankful, too.)
We want to be as productive as possible, so we want our code to run the first time; time spent in the debugger is time stolen from the development clock. It also helps if we can try out code as we edit it; if you have to wait for a 2-hour make cycle, you may as well be using punch cards and submitting your work for batch compilation.
…When we discovered Ruby … That’s how it can help you become a better programmer: by giving you the chance to spend your time creating solutions for your users, not for the compiler.
from: Programming Ruby
Python is very old. For backward compability some problems still exists: loop escape
The solution to some simple problems seems ugly: leet code reverse bits.
But it has good C/C++ interop, and pypi/wheels is a huge success, which also brings Hosting problems.