So I am back from my holiday experiments with Squeak and Seaside. I guess it's called experimentation because you are supposed to play without necessarily having a real agenda. This is a good thing because despite the fact that Smalltalk is a language I've been wanting to learn for a long time, and despite the fact that Alan Kay is one of my all-time computer heros (along with Ken Thompson and Dennis Ritchie and Knuth), I was sort of left ho-hum about the whole thing.
First, Squeak: while the idea of a fully integrated environment in a great thing in principle, Squeak is just too baroque and isolated from the surrounding environment (the web, the OS, etc.) for me to really envision using it as my primary development environment. From the trivial (the fonts supplied with it are just a complete eyesore) to the significant (in full screen mode on my 23 inch display the UI does not redraw correctly or respond to mouseclicks in a consistent way), the whole environment feels stuck in 1980. It may be better on Windows (I used in on a 2x2GHZ G5) but running inside a window in OSX made it's retro feel painfully obvious. The Squeak browser pales in comparison to Firefox and the web and basic OS-integration is sorely missing (sort of like Java apps from 3 years ago). The class browser looked like an awesome tool but too many things about the way you could scroll the panes was just broken in my view. And finally in some cases, like when grepping for a method name with the "method finder" the whole environment would just freeze up for 10-15 seconds at a time becoming completely unresponsive.
Then there was Seaside: Very cool idea, and probably a great implementation, but so sorely missing in documentation that it's pretty hard to go beyond the basic trivial counter application. I was particularly interested in how the continuations-based pattern for web development dealt with persistence (beyond with keeping things in RAM on the image) and concurrency (users working with the same model object at the same time) but I found little help in either case and it was not immediately clear to me from browsing the class hierarchy how this was supposed to get done.
The one thing that Seaside did have which is worth copying was a really neat way to inspect all of the page fragments (or widgets) from the web browser (outside of Squeak) including a fully web-based class browser. This was pretty awesome and it's a testament to Seaside (and a discredit to Squeak) that I found it better to work from the browser-based interface than in the cumbersome class browser-transcript-debugger inside the Squeak environment.
I still think that the Ruby-on-Rails podcast on Seaside with Avi is well worth listening to but I am not sure how he manages to be so productive with a tool that, at least after about 5 hours with it, seems so much like a university research project, and not a full-blown development environment. Maybe I lack the vision for it, but for now, I'm staying above the waterline for real work.