Nu Cardboard notes that even with IGB of RAM in their PC's, the Java apps they run eat the machines alive. The Eclipse IDE alone chews 300MB!

Now, contrast that with the Smalltalk system I use:

• A full development image running the blog server, the survey application, and a few other things: 142 MB of RAM. That's a full bore development image, btw - I have full access to all development artifacts there, on the remote server in Cincinnati
• The test server, which I run on a PII 400 - 63 MB. Go ahead, try running Eclipse on a PII 400.
• My BottomFeeder runtime application, with most of the development tools retained (I can open workspaces and write Smalltalk against the running application!): 110 MB

I think those guys made a sub-optimal choice in terms of development/deployment tools. The development image I use to work on BottomFeeder only chews 56 MB, and that's with all the code for it loaded into memory. The bottom line is, those of you who still think Smalltalk is "bloated" - you need to look again. There's bloat alright, but it's not over here...