| Well the coding universe is divided into 3 galaxies. The C galaxy that dominates desktop , the Java galaxy and the Javascript galaxy. Of course there are other galaxies too, but I think those 3 dominate currently. For C libraries you can use Pharo. Pharo has inherited 2 FFIs from Squeak and has implemented 1 additional FFI called Nativeboost which also allows you to inline assembly code for best performance. There is also the extra option of making VM plugin with smalltalk or C code which in turn interface with C libraries. For Java there is redline smalltalk, but it does not come with the IDE. It can use Java libraries out of the box. And for Javascript there is amber, it comes with the smalltalk IDE but its still a WIP, so its not as extensive as pharo. It can use javascript libraries out of the box. Smalltalk is a chameleon , its a language and an IDE made to fit in any case scenario. I think you will have a real hard time proving that its tool best used for specific scenarios, even in cases where OO approach is ideal, smalltalk approach could be ideal because it still has one of the most powerful OO systems plus refactoring tools, plus IDE, plus many nice toys. Smalltalk is that extremely rare case of software that it makes coding just flow, with no interruptions and no small annoyances. We call this style of coding "Live Coding" and its definetly the biggest reason to try smalltalk and even more try Pharo. Give a try and register in our mailing list, you will find many people passionate about smalltalk and yet a very welcome atmosphere for beginners. I am also a recent convert to Pharo from Python. I love Python but I dont miss it. So far Pharo has been very productive , fun and eye opening experience. You can find more info here -> http://www.pharo-project.org/home also a forum for the mailing list can be found here -> http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.ht... |
These couple of sentences give the reason that made me persist with Smalltalk (Pharo mostly). For those of you who come from, say Python, Java, C#..., this may be unsettling at first. The way you use the debugger to point you in the right direction and keep working without stopping. It feels all wrong in other, more pedestrian languages.