James is quite right here ... but there are many more hurdles and all these new potential users must be persuaded to come over these hurdles and be happy with it. * e.g. even in Eclipse you're sticked to the editor - nobody complains about it (one may write an additional plug-in) so this hurdle can be accepted - if the editor is attractive and gives you real power. In the area of editors in all those Smalltalk systems I noticed an improvement in the look-and-feel area - BUT they still do not offer additional helps like showing all possible methods for an object. In all (Smalltalk-) systems is the way to navigate to another class very long, that drives me mad. * the source code management problem seem to be a big hurdle. systems like svn, git, cvs are seen as open systems and are well known here. Nearly all ST systems have their own system (which are often far superior than the other ones). Source code exchange between all Smalltalk systems is worse ! Java, C and all that stuff would not be so attractive if the users have so many problems to switch from one Java-IDE to another Javae-IDE, or one C-compiler to another. * the language itselfs is getting old. Missing standard namespaces, missing interface specifications (etc) seems to stand for old languages. The missing of interface specification is the worst one and I do not understand the community, that nobody insist on adding this to Smalltalk. * Smalltalk systems are not well suited for multiprocessor, multithreading area ... * delivering process is more difficult than with other languages ... * we have problems getting access to successes in other languages. Out of the box it is difficult to interact with Java or .NET world. * even with the often propagated better productivity we are forced (due to the point above) to reinvent the world instead of being able to use already available software components. Considering all these hurdles - and then ask newcomers why should they use Smalltalk IDE xyz instead of Eclipse or VisualStudio (and both are available for more or less free and not copyright dialog and no runtime license problems). Am 29.10.2010 12:14, schrieb James Robertson:
I'm not sure that's the case. I used that line a lot when I was the Smalltalk Evangelist at Cincom, and it's true - up to a point. However, the prospective developer who looks at the tools from a personal use standpoint cares. So
-- the not quite "standard" widgets in VisualWorks make him think -- the "all in one windows" thing in Pharo and Squeak make him think
I don't think those are complete showstoppers, but they are hurdles - and they are additional hurdles the Smalltalk community doesn't need. Consider that we already present two big hurdles that we require people to get past:
-- The prospective user can't use his favorite editor -- The prospective user can't use his favorite source code control tools
the UI hurdle is something that could be dealt with (and yes, I recognize the difficulties). The last two are just there. Given that, the additional UI level one should be considered more seriously