It's fast enough for many use cases. That doesn't mean that there is no room for optimization, but this is far less a deciding factor these days.
> it's not type safe
You can do static analysis with Mypy and other tools.
> it has not real concurrency.
There's different mechanisms for running things concurrently in Python. And there's an active effort to remove the GIL. I also have to ask: What is "real" concurrency?
Admittedly, the things you mention are not Python's strongest points. But they are far from being dealbreakers.
>It's fast enough for many use cases. That doesn't mean that there is no room for optimization, but this is far less a deciding factor these days.
Everyone says this but its not really true. Every team I've seen do this immediately regrets it when they scale (like at all).
>You can do static analysis with Mypy and other tools.
Not even remotely the same
>There's different mechanisms for running things concurrently in Python. And there's an active effort to remove the GIL. I also have to ask: What is "real" concurrency?
Free threads. And yes this is a deal breaker in tons and tons of situations. I have no idea why people are soooo hard up for python
It's fast enough for many use cases. That doesn't mean that there is no room for optimization, but this is far less a deciding factor these days.
> it's not type safe
You can do static analysis with Mypy and other tools.
> it has not real concurrency.
There's different mechanisms for running things concurrently in Python. And there's an active effort to remove the GIL. I also have to ask: What is "real" concurrency?
Admittedly, the things you mention are not Python's strongest points. But they are far from being dealbreakers.