@collin I think they might have considered it a failure if it is true that users didn't get into modifying the software they were running. Devs not getting it might not have bothered them as much.
@rahoulb well, you tried 👍🏼
Taking the liberty of including @drgeo , who was bringing his software to #Smalltalk (tried #Pharo, switched to #CuisSmalltalk). i.e. knows a thing or two about developing in Smalltalk.
@collin @tetrislife @rahoulb In the Squeak babies, the GUI framework is not as polished as in GTK+ or Qt. It is not a problem of Smalltalk but the small communities.
Among the Squeak babies, it is in #CuisSmalltalk you find an easier to understand and cleaner Morph framework (really a lot). There are some efforts with Cuis-Smalltalk-UI to develop its set of Widget.
@tetrislife @collin @rahoulb There were also an intial Squeak version running on the OLPC.
#CuisSmalltalk if for my need the most appropriate. I like smaller and cleaner environment. There are way too much legacy code in Squeak and Pharo.
@drgeo @tetrislife @rahoulb I need to spend more time with #CuisSmalltalk. It does seem like the simplest.
@collin @tetrislife @rahoulb there is "The Cuis book", a gentle introduction to #CuisSmalltalk
@tetrislife @rahoulb @drgeo I think that's totally what they wanted, and clearly there are people who enjoy it, but to me, it actually makes things more confusing. Like what's cool about Smalltalk to me is that it's so minimal and there's not a lot to remember about the language, but now there's all this other visual stuff and how to kind of penetrate it is not super clear from the outside.