3 ms·
I poked around at it in the past, and the biggest impediment I found was the need for opaque and specialized development tools. This may not be universally tru
by mindcrime 11y ago
I poked around at it in the past, and the biggest impediment I found was the need for opaque and specialized development tools. This may not be universally true, but from what I saw, most Smalltalk environments require you to use their specific IDE/editor, and then it saves your code in some proprietary (binary?) format. So it's not as simple as just editing a file with Emacs or Vim and running
#> smalltalk myfile.smtlk
or whatever.
Beyond that, it's just quite a bit different from a lot of other languages people might be familiar with, like, say, C or Python. OTOH, it's not any more different than Lisp.
I always heard good things about Smalltalk, but there was never anything so compelling that it swayed me into investing the time to learn it. But I'm open to being convinced, even now.
- csdcasder 11y agoTake a look at Pharo. I did and Pharo is now my primary personal development tool. Another thing that convinced me were videos by Laurent Laffont. Laffont uses Pharo, IMHO, the way it is supposed to be used - he uses the debugger intensively during development to prompt him to for the next step. His development workflow is guided by a general outline in his mind, and the details are filled in by the debugger prompts. His videos can be found at Pharocasts.
- mindcrime 11y agoOK, I'll check it out. Thanks for the heads-up.
- horrido 11y agoYes, it's true. Most Smalltalk dialects use a special IDE. This is because the biggest advantage of using Smalltalk for development is the "live" programming environment where you can examine any object in the executing program (thanks to Smalltalk's astonishing reflection capabilities) and you can alter the running code and watch the results in real time. This is not possible with conventional, file-based tools such as Emacs or Eclipse. Smalltalk development is a fundamentally different paradigm from the conventional, file-based development process. It does require you to adapt to a new way of doing things, but this confers fantastic benefits. The combination of super-simple and elegant syntax with a powerful IDE makes developers much more productive than programming in Java or C++ [1]. Having a simple syntax minimizes the cognitive load on the programmer, making it very easy to master the programming tool. When you master your tools, you work at maximum efficiency and effectiveness. However, if you really must use your file-based tools, there is a command-line Smalltalk called Gnu Smalltalk. IMO, however, giving up on live programming is too great a sacrifice just for this obsession with file-based editors and tools. [1] https://smalltalkrenaissance.wordpress.com/2015/02/16/smalltalks-proven-productivity/ https://smalltalkrenaissance.wordpress.com/2015/02/16/smallt...