> Second it depends on what your or your teams experience level is.
+1.
I work in a Skunkworks department inside a larger/older company and we recently decided to stop using Python in the future, the company's language.
Node.js, Go, Rust, C#, etc, all of those are extremely boring for us. They're stable and we get things done in minutes. In Python it's like pulling teeth, with constant API changes and refactors from other teams we're struggling to keep up with. Which one is boring? For us, not Python.
The Python developers naturally disagree and say "there must be something wrong with your team if you can't use Python at the same speed and efficacy as us".
Python is fast for tiny programs. However if you have more than one team it isn't tiny. One developer can make something not tiny in a few weeks. For large programs a compiler that checks syntax, and ideally types before you run a comprehensive test suite ( which probably isn't comprehensive enough) is nearly mandatory to be maintainable. Otherwise you can never be sure you adjusted everything when you need to change an API.