Every time a component in seaside is rendered there is an opportunity to set the url. It can be useful for some apps to not have to worry about this either dur

Every time a component in seaside is rendered there is an opportunity to set the url. It can be useful for some apps to not have to worry about this either during some phases of dev or ever. seaside is continuation centric. You have to fight the system to get around for those occasions when it really won't suit. It would be nice to see a next-gen seaside like framework that gave the programmer flexibility in when continuations are used. There are aspects of the framework that show a wear and cruft and would benefit from a clean-room rewrite a la rails3/merb2. That said, Smalltalk and the latest Pharo is a joy to work with.