I still like terminals, mostly out of necessity. Terminals are effectively guaranteed to be there when all else fails: whether that be due to a misconfigured c

I still like terminals, mostly out of necessity. Terminals are effectively guaranteed to be there when all else fails: whether that be due to a misconfigured computer, or to a slow connection that means that you're using SSH only, or because you're stuck using a rubbish chromebook linked to your Real Computer back home via SSH (which happens to me a lot). So while I admire things like acme and smalltalk, my personal philosophy, partly for flexability, and partly out of necessity, is that if you can't run within a terminal window, I can't depend on you, or integrate you too heavily into my workflow. Because when I need you most, you'll let me down. This is the second reason I hate most IDEs, by the way. The first reason is that most IDEs believe that if your language is verbose, the solution is more automated code generation. I believe that if most of your code is being generated automatically, you need a new programming language. Naturally, the Smalltalk IDE gets a pass, because it's not an IDE in the common sense. It's more like a real-time introspective debugging environment which you happen to write all your code in. It's not even technically required for the language, as GST aptly demonstrates. But the first time you use the smalltalk debugger, you'll be sold on it. You'll want it thr smalltalk IDE in every language. Sadly, this isn't possible, unless you're a lisp programmer with either A) a lot of money or B) a lot of spare time on your hands, you can't have it.