This is an argument for unit tests, not for a statically typed language.
Type errors tend to be very few and far between compared to logic errors.
Multiple processes in most web applications are best handled by a pre-forking webserver in front of something like mod_wsgi, and using an engine like Celery for asynchronous and long-running operations on the backend, often launched with something like supervisor.
I do take issue with some parts of the article, namely saying there is a good type system (there's not, but it's all fine, duck typing, etc) and that twisted is a good framework.
It is definitely true however that Python is a great fit for all kinds of serious applications, but with all things, it takes discipline.
Type errors tend to be very few and far between compared to logic errors.
Multiple processes in most web applications are best handled by a pre-forking webserver in front of something like mod_wsgi, and using an engine like Celery for asynchronous and long-running operations on the backend, often launched with something like supervisor.
I do take issue with some parts of the article, namely saying there is a good type system (there's not, but it's all fine, duck typing, etc) and that twisted is a good framework.
It is definitely true however that Python is a great fit for all kinds of serious applications, but with all things, it takes discipline.