3 ms·
Put simply: because the things that made Smalltalk great are now part of modern stacks. Dependency management, interactive development tools, object-browsing ID
by poulsbohemian 12y ago
Put simply: because the things that made Smalltalk great are now part of modern stacks. Dependency management, interactive development tools, object-browsing IDEs, plus virtual machines improved significantly. Why go back to Smalltalk when we have all of these things with the language of our choice today?
- masukomi 12y agoBecause smalltalk integrates those things together better than any other language / environment that has them?
- poulsbohemian 12y agoDon't get me wrong - I'm thankful that I got to use Smalltalk in my career. It was incredibly expressive and productive - maybe the most productive I've ever been. But, time marches on. There are simply more people working today on python / node / <pick_your_favorite_here> to maintain and improve those tools plus making it easier to find a <language> programmer over a Smalltalk programmer.
- fizfaz 12y agoout of interest, which modern stacks allow "live coding" your application? That is: no need to restart for various changes you make. You are playing/changing/creating with the objects that make your aplication. I am currently doing mostly Objective-C-programming in Xcode, which is a rather simple IDE in this respect. In the past I used more java, but at this time only simple changes were possible live (using Eclipse back then), for a lot of others I had to compile and restart anyway.