Python improvements are on par with ruby, and ruby has a JIT, which means that upside fir real world improvement is much higher. Python has no static typing. I

Python improvements are on par with ruby, and ruby has a JIT, which means that upside fir real world improvement is much higher. Python has no static typing. It has type annotations, which a few 3rd party static analysers such as mypy use. Ruby has had the same since 3.0 with rbs. The ecosystem may be less mature, but it exists, and Python's isn't necessarily perfect. Python async is terrible. You have to colorize functions, opt out from a significant part of the ecosystem which either does not support async, or is very unstable, and completely relearn how to do debugging / performance measurement. Ruby has smth better since ruby 3.0, via the fiber scheduler, which supports running network related code asynchronously with *no changes or special function annotations*. Ruby packaging has been figured out since 2007, and has been influencial for other ecosystems, being the first mainstream language adopting lockfiles. If you prefer using Python, you are entitled to your opinion and choice. But those arguments are all FUD.