There is this phenomenon, when people confuse upgrade over previous iterations, with the hottest shit ever.
I think this has happened with Java style OOP. It came in existence to fix some things, became "the way to do programming", but honeymoon is over now.
We might see it happening now with gradual typing. Dynamically typed languages are being upgraded with some static typing, and you can see comments popping on HN how this is actually the best way of writing programs.
Rust is in this category and a dose of skepticism is always welcomed.
(Good) static typing is the single most useful thing of any programming language. A large, disorganized project in Java is far better than the same thing in Python or Ruby.
Python is fine if you have a good IDE and a very strict type checker config. I use the most strict configs I can manage and it's almost at par with static typed languages, at least where you're developing and refactoring. Runtime is another matter altogether, though I've never had problems with Python once I have ensured types going in and out match and validate inputs.
The problem with Python type checking is that the general community still does not write libraries with types. On the other hand, the JS community is further along and most libraries written today include TS files. I think the same will happen with Python, but it obviously takes time.
I think this has happened with Java style OOP. It came in existence to fix some things, became "the way to do programming", but honeymoon is over now.
We might see it happening now with gradual typing. Dynamically typed languages are being upgraded with some static typing, and you can see comments popping on HN how this is actually the best way of writing programs.
Rust is in this category and a dose of skepticism is always welcomed.