So I followed a great example and cooked up a couple screencasts.
The first presents Seaside as a Web app IDE, one of the very cool things about it which sometimes gets overlooked in the discussion about it -- and I sometimes suspect the number of people talking about Seaside is larger than the number of people using it -- and the second addresses that whole Rails vs. Seaside thing in much greater detail. (I promise it isn't another language war.)
First screencast: 4 minutes:
Seaside is a framework and an IDE
Second screencast: 12 minutes:
Seaside and Rails
Update: turns out I'm wrong -- you can do REST in Seaside.
Update 2: I moved the screencasts to S3.