i kind of agree. i use pharo, and i love working with it. it is actively developed and its interface is improving with every release.
what i like about it though, is not the IDE but the image based development:
that i can debug and fix an application while it is running.
that, for certain classes of errors, i can pause an application (or it will pause by itself), and simply resume after fixing the error.
maybe 10 years ago, and certainly 20 or 30 years ago, smalltalk's IDE was ahead of its time. today, many alternatives exist.
but image based development is limited to very few platforms. only smalltalk, lisp and a few others offer that.
i also like that smalltalks syntax is incredibly minimalistic.
the downside is that smalltalk effectively requires you to forget all the tools you worked with before. but this is again, where pharo development makes its mark. it is now well integrated with git for example.
we all know that git has its issues and a learning curve, and many GUIs are trying to make git more accessible. pharo managed to integrate git in a way that it works well with the traditional smalltalk development style while at the same time allowing it to take advantage of the strengths that git has to offer.
greetings, eMBee.