Few months ago I started a comparison of Aida, Seaside and Iliad web
frameworks, with initial goal to check the strengths and weaknesses of
Aida to draw a direction for future Aida development.
But later I came to idea (and was encouraged also by Stef and others) to
improve it and make this comparison public, therefore for all of you. I
then invited few Iliad and Seaside guys to help balance the comparison,
but unfortunately Seasiders were not willing to join, with their stated
reason that spreadsheet of comparative features is not the best way to
do such comparison. My answer is that a form of spreadsheet is a
simplest start of such comparison. This feature list and check marks can
be later a foundation for some more advanced comparison. We need to
start from somewhere and such checkmarked spreadsheet is easiest to
achieve in a shortest time.
So, now I'm inviting all of you to take a look at this Google Docs
spreadsheet and comment it. This way we will come at least one step
closer to so needed comparison:
Smalltalk Web Application Server
It is hard to expect from us others to merge into if even its author
admits that Seaside is now obsolete. That is, (from Avi words )
Seaside was advanced at the time it was designed, but now it lags behind
advances. It is therefore better for Seaside to rather listen to its
author and do something. Or merge already done ideas from us others instead.
Common guys, Ajax is 5 years old, let the Seaside finally come with Ajax
support at least close to that in Iliad and Aida! Then study carefully
what Nicolas Petton and his group is working on Iliad and Jtalk. We are
doing so and incorporating but also extending his ideas in Aida. And on
the other way too, Nico is listening what we are doing. Why not you too?
The most popular Smalltalk web framework sleeping on the successes in
past is namely bad for all Smalltalk, that's why I'd like to open the
debate about the web support in Smalltalk in general.
On the web we have an opportunity, are we loosing it?
That's why I'm pushing this comparison and that's why I'd have and ESUG
talk titled "On the web frontiers with Smalltalk". And a panel is
So, Seasiders, come to the web frontiers again by looking what
we others are doing, learn and adopt. And contribute some own innovative
ideas to the Smalltalk on the web again!
S, Boris Popov, DeepCove Labs piše:
> You nailed it. We all know that Smalltalk community is small and, quite
> possibly, getting smaller, whether we like it or not. The exposure that
> Avi had given to Seaside resulted in a good mass of developers coming on
> board and it becoming a de facto web framework for developing dynamic
> and powerful applications in Smalltalk. Given the state of things today,
> I would honestly much rather see competing frameworks converge on a
> single path and their developers contribute to improving Seaside in
> hopes of it continuing to sustain or gain traction, similar to how RoR
> had pretty much taken over in Rubyland.
> *From:*[hidden email]
> [mailto:[hidden email]] *On Behalf Of *Nick Ager
> *Sent:* Tuesday, June 21, 2011 5:59 PM
> *To:* Seaside - general discussion
> *Subject:* Re: [Seaside] Comparison of Aida/Web, Seaside and Iliad web
> Hi Janko,
> What are you trying to achieve? Is the idea that we come up with some
> feature comparison, add up the ticks in the supported column and declare
> a winner?
> I joined the Smalltalk community because of Seaside or rather because of
> Avi Bryant's, Lukas's and others magical demonstrations that Seaside
> offered a compellingly more productive way of developing web
> applications. Some of the reason I continue to choose Seaside over other
> * Component based
> * State management
> * DSL for Html generation
> * Neat integration with Scriptaculous and now JQuery for AJAX
> * #call, #answer semantics
> * active, friendly and technically deep development community.
> The question we should be asking ourselves is what compelling features
> can we develop which will attract a set of new developers to Smalltalk,
> otherwise it feels like we're bald men fighting over a comb.
> seaside mailing list
> [hidden email]
Smalltalk Web Application Server
+n, couldn't agree more
Sent from android 2.1
On 22 Jun 2011 14:11, "Janko Mivšek" <[hidden email]> wrote:
In reply to this post by Janko Mivšek
S, Runar Jordahl piše:
> Come on… We all know Janko is biased, and the comparison reflects that.
> But it is not like he wants to take over the world and kill Seaside.
> Well… maybe he wants, but there is still no reason to get upset. :-)
I'm biased by definition and I don't hide that :) See disclaimer right
in the header of comparison.
But let me explain my rationale: I started this comparison to assess the
strengths and weaknesses of Aida comparing to other two. And I need to
know Seaside and Iliad for competitive reasons which is a strong
motivator for learning other frameworks. End result is also that I can
actually compare them very well. But from my own perspective of course.
Which I stated upfront 100 times already: This comparison is Aida centric!
At the end all community have something out of that comparison even if
it is biased. Better than nothing, I like to add :) And I invited you to
> I have only tried Seaside, choosing that framework since it is the
> “default” one to use for Smalltalk web development. At least the
> comparison made me aware of Iliad, and had me rediscover Aida. But even
> if I now have more knowledge, I am more confused than ever.
> We need some small reports, from various sources, comparing the
> strengths and weaknesses of the frameworks. Creating a collaborative
> to-do-list application might be a good reference case.
Agreed, someone from a distance should look at all three and study
matarials like this comparison and forthcoming examples. I expect
someone from academic world to step up ... ;)
About ToDo example, Hannes prepared nice requirements at
http://www.edupad.ch/tB6G15hqCx and I'm near done it in Aida. Expect in
a day or two the announcement. A live multiuser ToDo for you to look at
together with published code.
> From what I understand, all three frameworks generate HTML using roughly
> the same techniques. But there are differences in how you compose a page
> from multiple components. The spreadsheet mentions “composition” vs.
> “rendering”. Getting a short discussion about these concepts is probably
> more helpful than a lot of (smaller) features compared.
Good idea. Let we start about HTML generation in a separate thread.
> explaining how the various frameworks handle this and how they will
> tackle it in the future, is important. It seems like Aida and Seaside
> takes different routes here. How does that matter for me as a user?
> Again, a more detailed discussion than “yes” / ”no” on a feature list,
> would be welcome.
Discussing here the certain feature is probalby he best way to achive
better explanation of each feature or group of features. Let we start
with above one for now.
> It is also interesting to see how this thread discusses the future of
> Smalltalk web frameworks. As I understand this, we have Aida, Iliad and
> Seaside being the “server-centric” web frameworks. These frameworks
> to provide a richer UI experience at the client. Then we have
> Quicksilver and Jtalk which basically let you run your UI (Smalltalk)
> code in the client browser itself. These “client-centric” frameworks are
> experimental and not ready for production. As Janko mentions,
> integration between these two types of frameworks will be important.
Exactly. Jtalk is currently in full and very hot development, with a
goal to be included in Iliad soon. And in Aida too, I have great plans
with it. Not only on client-side: with Jtalk we can conect to wast
amount of node.js modules on server-side!
> Kind regards
> Runar Jordahl
> blog.epigent.com <http://blog.epigent.com>
Smalltalk Web Application Server
|Free forum by Nabble||Edit this page|