Because most of the work for Seaside (and to a similar extent Rails) is in managing user interface state. That goes away with client side frameworks. At least most of the messy complex stuff - obviously persistence things are still kinda handy ;)
Its back to the future.
When you have worked with both you find that the back end stuff just gets in the way for the rich client frameworks. Its not to say that "classic" action/restful style web apps don't have a place (they have a BIG place, especially for content heavy sites) but its not a one size fits all.
Its back to the future.
When you have worked with both you find that the back end stuff just gets in the way for the rich client frameworks. Its not to say that "classic" action/restful style web apps don't have a place (they have a BIG place, especially for content heavy sites) but its not a one size fits all.