> once you use an IDE that actually IS "integrated" as the acronym suggests, you will never turn back. If you're unfamiliar with Smalltalk environments and are

> once you use an IDE that actually IS "integrated" as the acronym suggests, you will never turn back. If you're unfamiliar with Smalltalk environments and are wondering what this actually means, watch this 3-minute video showcasing a Smalltalk IDE -- the class browser, method finder, and debugger: http://vimeo.com/27850933 http://vimeo.com/27850933 Anything else seems so... primitive by comparison. Smalltalk's great drawback is over-reliance on the image: "If your program misbehaves (and they always do) and corrupts the state of the process, things get tedious. Say you have a test that somehow failed to clean up properly. In a conventional setting, you fix the problem with your code, and run the test again. With an image, you have the added burden of cleaning up the mess your program made. [...] In general, Smalltalk makes it hard to [...] separate the application from the IDE." -- http://gbracha.blogspot.com/2009/10/image-problem.html http://gbracha.blogspot.com/2009/10/image-problem.html