Thanks for the insight. I didn't realize that ruby's (former?) continuation memory-leaks were the the reason for Seaside being in Smalltalk rather than Ruby.
In this case I wonder whether Smalltalk really is the right tool for the job. Smalltalk isn't a bad language but there aren't a lot of libraries available. I've played around with Seaside a bit and ended up having to rewrite some of the HTTP libraries to do what I needed. Unfortunately I can't think of another language outside of the LISP family that supports continuations well.
In this case I wonder whether Smalltalk really is the right tool for the job. Smalltalk isn't a bad language but there aren't a lot of libraries available. I've played around with Seaside a bit and ended up having to rewrite some of the HTTP libraries to do what I needed. Unfortunately I can't think of another language outside of the LISP family that supports continuations well.