Yeah, except without all the bad parts like images that can get corrupted
Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.)
stateful (wtf were they thinking?) web-apps.
Same things others were thinking at the time -- you're just seeing a slice of history. People still rave over the debugging in Seaside like it's magic, though.
All the benefits of a Lisp REPL and a Smalltalk debugging environment in a language people actually use. Tab-completion, dumps, breakpoints, testing assumptions/data, running arbitrary code inside a specific environ...the works.
I can use it in my virtualenvs without having to explain to an IDE what a virtualenv, a running test in Nose, a normal script, or a running web server. It's normal code so I can wrap the trace in a condition or whatever else I want.
No, I'm wondering if the promulgators of Smalltalk as a superior debugging environment actually have anything superior to what I just described so that I can steal it for Python.
Sometimes I toss stuff out there in the hopes of being shown something better. It's teaches me new things.
Lets take a moment to think on our poor brethren still tossing print statements all over the place though.
Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.)
stateful (wtf were they thinking?) web-apps.
Same things others were thinking at the time -- you're just seeing a slice of history. People still rave over the debugging in Seaside like it's magic, though.