Seaside vx Ruby vs Ajax vx ?

> I'm working on an article on Seaside for DevSource (which is oriented  
> around Windows programmers, but which the editors have also found
> that  actual code, regardless of platform, is more attractive to
> readers than  anything else) and was wondering if anyone here had any
> experiences they  wanted to share on using Seaside versus using other
> technologies.
>
> It appears to me that all these technologies are primarily concerned
> with  preserving state in the stateless environment of the web. Is
> there more to  it than that, really?
>
> Also, is there an advantage, do y'all think, in Smalltalk having a
> plug-in  VM? That is to say, do you think it's easier to segue from
> Seaside to a  rich-client type experience in Smalltalk than these
> other technologies?
>
>

> Blake wrote:
>
>> I'm working on an article on Seaside for DevSource (which is
>> oriented  around Windows programmers, but which the editors have also
>> found that  actual code, regardless of platform, is more attractive
>> to readers than  anything else) and was wondering if anyone here had
>> any experiences they  wanted to share on using Seaside versus using
>> other technologies.
>>
>> It appears to me that all these technologies are primarily concerned
>> with  preserving state in the stateless environment of the web. Is
>> there more to  it than that, really?
>>
>> Also, is there an advantage, do y'all think, in Smalltalk having a
>> plug-in  VM? That is to say, do you think it's easier to segue from
>> Seaside to a  rich-client type experience in Smalltalk than these
>> other technologies?
>>
>>
> Speaking of Ruby, etc.... Ruby and AJAX are receiving more and more
> press these days. There was an article this weekend about Michael
> Arrington's site: TechCrunch (www.TechCrunch.com) entitled "Web 2.0."
> Ajax and Ruby were mentioned. Although it was a business article and
> not technical in nature, the press seems to be piling up for these two.
>
> From http://www.theopensourcery.com/ajaxdirections.htm I get a clearer
> overview of AJAX. Is there a FAQ on the plus/minus of Seaside over
> Ruby over AJAX? I think this has been discussed  briefly here (see
> thread: "ajax...an idea to squeakize! and "LiveWeb") and this is
> informative: http://smallthought.com/avi/.
>
> Why should someone choose/not_choose Seaside over the buzz of today
> (Ruby or Ajax.) If there are clear advantages, or even specific
> advantages for web developers in certain situations, it would be nice
> to get the word out.

>On 1/16/06, Brad Fuller <[hidden email]> wrote:
>  
>
>>Why should someone choose/not_choose Seaside over the buzz of today
>>(Ruby or Ajax.)
>>    
>>
>
>Seaside includes Ajax-y things - you can do asynchronous processing
>without writing a single line of Javascript.
>
>(In fact, I used 'Ajax' in a VAST WebConnect project, and I'm quite
>sure that the IBM guys never considered that possibility. Ajax,
>stripped to the core, is dead simple)
>
>Ajax is the most overhyped thing at the moment. My predictions for it
>are, therefore, dire. I will bet it will go the way of XML - simple
>and interesting at first, then the "Enterprise" folk run away with it
>and within 2 years we have W3C AJAX standards that span 1000 pages.
>Wanna bet?
>
>In the meantime, XMLHttpRequest is a nice feature. It can really help
>to make web applications more usable. Use it in any environment (want
>to see "CGI Ajax support"? Takes a whopping 1 minutes probably to
>implement it).
>
>Ruby or Smalltalk? I'm a productivity whore and relatively immune to
>hypes. So I prefer Smalltalk. YMMV.
>  
>

>
> Speaking of Ruby, etc.... Ruby and AJAX are receiving more and more  
> press these days. There was an article this weekend about Michael  
> Arrington's site: TechCrunch (www.TechCrunch.com) entitled "Web  
> 2.0." Ajax and Ruby were mentioned. Although it was a business  
> article and not technical in nature, the press seems to be piling  
> up for these two.
>
> From http://www.theopensourcery.com/ajaxdirections.htm I get a  
> clearer overview of AJAX. Is there a FAQ on the plus/minus of  
> Seaside over Ruby over AJAX? I think this has been discussed  
> briefly here (see thread: "ajax...an idea to squeakize! and  
> "LiveWeb") and this is informative: http://smallthought.com/avi/.
>
> Why should someone choose/not_choose Seaside over the buzz of today  
> (Ruby or Ajax.) If there are clear advantages, or even specific  
> advantages for web developers in certain situations, it would be  
> nice to get the word out.