Absolutely right. Pharo isn’t perfect, either…

1. Pharo is dynamically typed. If you prefer static typing, then Pharo is not for you.
2. Pharo’s execution performance falls far behind that of languages like C, C++, Java, and C#.
3. Pharo doesn’t support preemptive multithreading the way Go and Erlang/Elixir do.
4. Pharo lacks support for separate namespaces.
5. Pharo is garbage-collected which makes it less suitable for critical real-time applications.

But like Python, Pharo is very usable for most application domains. I still prefer Pharo over Python.