[squeak-dev] Re: [Newbies] Seaside vs. AIDA

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: [Newbies] Seaside vs. AIDA

Brad Fuller-4
I've copied this reply to the squeak-dev mailing list. There have been
some recent discussions on both

On Thu, Mar 20, 2008 at 11:14 AM, Leon Smith <[hidden email]> wrote:

>
>  I don't want to start a war here, but I have been through the first steps
>  with both Seaside and AIDA/Web, enough to build the start of a web site.
>  Before I make the commitment to one or the other, I wonder if anyone has
>  done a recent, objective comparison between the two ?
>
>  They both seem very capable. I felt like I turned out a better looking
>  product a little easier with AIDA, but I sense that Seaside has a much
>  larger following. I also wonder if continuations are that important to me.
>  They also have a great many similarities. To the point where I think I could
>  change AIDA to use a lot of Seaside if not the other way around.
>
>  Any real experiences between the two will be most appreciated. This is a
>  major decision point for me.
>
>  Leon
>  --
>  View this message in context: http://www.nabble.com/Seaside-vs.-AIDA-tp16185376p16185376.html
>  Sent from the Squeak - Beginners mailing list archive at Nabble.com.
>
>  _______________________________________________
>  Beginners mailing list
>  [hidden email]
>  http://lists.squeakfoundation.org/mailman/listinfo/beginners
>



--
Brad Fuller
www.bradfuller.com

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: [Newbies] Seaside vs. AIDA

Nicolas Petton
Hi,

being an Aida dev, I can't be completely objective, but I used Seaside
in the past too.

Both frameworks are great, powerful and mature, and I know how hard it
can be to choose.
IMHO, you can do the same with both, but they answer different needs.
Aida keeps things simple, and follows web rules like REST urls. Seaside
is very different. It doesn't use REST, and strongly uses continuations,
but it is closer to "standard applications", you don't think in terms of
pages or templates, but call/answer between components.

However, they have some similitudes. They both use components for view
rendering, you don't have to write html code, they both have js
libraries integration like Prototype and Scriptaculous for example.

Another thing, and this is still my personal opinion, I think that Aida
is a lot easier to use and learn, and also has built-in features like
users, group ans security management, while Seaside doesn't.

Maybe the best question to ask is what do you need? If you need
meaningful urls, using Seaside may be a bad idea (It is not impossible,
though, look at Pier or WABrowser for example). If you want to develop
web applications like you would do for standard ones, Seaside could be
better.  

I hope this helps.

Cheers!

Nico
--
Nicolas Petton
http://nico.bioskop.fr
            ___
          ooooooo
         OOOOOOOOO
        |Smalltalk|
         OOOOOOOOO
          ooooooo
           \   /
            [|]
--------------------------------
Ma clé PGP est disponible ici :
http://nico.bioskop.fr/pgp-key.html



signature.asc (196 bytes) Download Attachment