If you are doing a CRUD style app, you aren't going to get as much from Seaside. If you shared state- required etc. Seaside/Weblocks will be a dream, you'll be amazed how quickly you get things done that took so long in the Djanjo/Catalyst/Rails style.

I love how Seaside has changed they way I think about web dev.

What are some web apps that don't have a CRUD model to them?

Well by CRUD, I really meant and should have said, simple CRUD. blogs, twitter etc where you basic interaction is short.

Things that can not simple CRUD:

multi step e-commerce order application, games, anything that relies on your previous action to decide what happens now.

a blog doesnt care what I did before, neither does twitter or myspace or facebook. Do this thing, store result. 1 page to result usually. Simple CRUD.

If you do simple CRUD, you probably won't get a ton of value from Seaside/Weblocks. If you are doing applications where stateful is required/desired and RESTful is hard, both will be wonderful to work with.

Why is RESTful desirable?

There is a mass of blog posts etc about why RESTful can be a good thing ( even if many get REST somewhat wrong ), I don't think anything is going to be gained by my trying to fit all that information into this small textarea.

Was hoping context would narrow things down. Sorry. :\