Tuesday, October 11th, 2005

Weighing up the Rich Client alternatives

Category: Articles

Alexei White has given his opinion on the various rich client technologies out there (Ajax, XUL, XAML, Applets, Flash, and SVG) giving pros and cons to them.

He then attempts to answer “Why Ajax now?”:

Ajax is a natural choice for four reasons:

  • 1. It solves current business problems.
  • 2. Platform independance.
  • 3. Skill-set comformity.
  • 4. Network effects.

Has he got it right?

Posted by Dion Almaer at 9:48 am
4 Comments

+++--
3 rating from 5 votes

4 Comments »

Comments feed

“Has he got it right?”

Who knows? Where on the hype curve do you suggest Ajax currently is?

Comment by a — October 11, 2005

i’m not sure if you can compare ajax to any of the other mentioned technologies. in my opinion ajax on it’s own is not a framework to build rich clients. you still need all the other technologies like dhtml, css, etc. on the other hand you can use xul and ajax together to build rich clients.

i think you can only mention ajax in addition to any of the other technologies.

Comment by anonymous coward — October 12, 2005

for me it comes down to comparing the HTML DOM as a “canvas” to SVG, XUL, XAML, XForms etc. Today the AJaX pattern is most commonly used with DHTML since it plays nicely with XML, CSS, JavaScript etc and therefore (for me) the AJaX moniker has an implicit connection to DHTML.

Comment by Dave Johnson — October 12, 2005

It’s correct to say that these are not mutually exclusing approaches or ‘technologies’, but the interesting thing about ajax it can almost be an end-to-end solution for the front-end. You’ve got your data connection, an interpreted language to compute with, and a presentation interface. So if we look at it that way we can start to closer comparisons to XUL, SVG, etc..

Otherwise we’re left with few ways to make a critical evaluation.

Comment by Alexei — October 12, 2005

Leave a comment

You must be logged in to post a comment.