I'm sure this comes up with many less main stream languages - I think there is a strong argument (particularly if we get the GitHub piece operating smoothly) that the language is so simple that what you creating is domain understanding (not language/tools prowess). Any good developer (particularly a Ruby, Groovy, JS, Objective C or even Python) dev will find Smalltalk a doddle. The complexity is actually in the domain. We also have a vibrant and active community that has been around a long time and is willing to help as well as lots of free online training materials. Put another way - you can use a language like Java but if you left, the complexity of build and deployment and understanding the domain is a huge hurdle even though it's s popular language. I've dipped in and out of Smalltalk throughout my career and a few years ago came back after 10+ years (so had basically forgotten most of it) and was stunned that I was productive in that team after 1 day once they showed me how to inspect items in the UI and navigate to tests. I've never encountered that on a project before. Tim Sent from my iPhone
On 19 Oct 2017, at 08:04, Paulo R. Dellani <dellani@pobox.com> wrote:
Dear all,
after using Smalltalk for several years I developed a passion for the language (how not to?), and Pharo is just so great to develop with. So thank you guys for keeping this wonderful project running.
Unfortunately, it is not easy to always point out why Smalltalk should be employed as "main development language" in a team or for a project. In the last discussion of this sort I was confronted with the question "where are we going to get new smalltalk developers if our startup grows or if you go?". Well, I had no good answer to that. What would have you answered?
Cheers,
Paulo