Monday, May 15th, 2006

134 Ajax Frameworks and Counting

Category: Ajax, Toolkit

Michael Mahemoff spent the past few days at the Ajax Experience conference and came to a slightly surprising revelation as he prepared for his talk on Ajax design patterns and principles.

I just did a quick count of frameworks and libraries on the wiki. Turns out there are 58 in pure Javascript and another 76 with back-end support in PHP, Java, or whatever. This includes 13 for .Net, and no less than 22 for each of PHP and Java.

Overall, that’s 134 Ajax frameworks and libraries out there, many of them under a year old! It’s true that a few of the pure Javascript libraries are things like Drag-And-Drop that have been around a few years, but only a few of those. The rest are all-encompassing, like Dojo, or related to remoting, like ACE, or related to XML and DOM manipulation in a manner closely associated with Ajax, like logging and effects libraries.

He also notes that, in December he created an appendix of frameworks that came to 90, and now that number has grown up to the 134 he mentioned previously – “So roughly 45 new frameworks since then, about one every three days.”

It’s wonderful to see that Ajax isn’t loosing any steam as time goes on. When it first started up, early adopters/framework creators were looked at as just “wasting their time” on another flash in the pan. Now it’s those early adopters that are on the cutting edge of something that others wished they’d latched onto sooner.

Posted by Chris Cornutt at 7:17 am

3.7 rating from 71 votes


Comments feed TrackBack URI

Someone needs to get to work on a nice big chart with the different toolkits and what they support, etc, that way we can compare at a glance.

Comment by Allen — May 15, 2006

Our Javeline Framework has been under development for 5 years now, but we have only recently released it (after about 3 full-rewrite iterations).. My guess is many frameworks will require rethinking quite a number of times too. It is time ‘AJAX frameworks’ are to be compared on what they actually are. Based on the architecture, components, stability, ease of use, etc.. besides being called an ‘ajax framework’ which currently says almost absolutely nothing. I second the ‘comparison chart’ :)

Comment by Rik Arends — May 15, 2006

There was kind of a running joke at The Ajax Experience about how each speaker at some point exhorted people to take advantage of frameworks/libraries.

During the second panel, about 1/3 of the audience put up their hand to indicate they’re (only?) using their own stuff. Since not everyone at the conference is actively developing Ajax apps, this suggests about 50% of people there are using their own “toolkits” (read: frameworks+libraries). Some people I met do so because they’ve been developing Ajax apps a long time, before they existed. The majority, though, probably found it the easiest path to begin. If the conference is anything to go by, the message to use frameworks and libraries will become more clear in the next 12 months. Also, the Ajax libraries’ maturing will help them get more play in Ajax textbooks.

Comment by Michael Mahemoff — May 15, 2006

[ajax] 134 種のフレームワーク Ajax関連のフレームワークとライブラリを調べてみると, 58 in pure Javascript and another 76 with back-end support in PHP, Java, or whatever. This includes 13 for .Net, …

Trackback by ma2の日記 — May 15, 2006

Interesting Finds

Trackback by Jason Haley — May 16, 2006

I’m happy, but not sure about all that excitement about 134 different quite-brand-new frameworks.. Small development teams – or single coders – can’t reach a really conscious choose about one of them, they’re too much and too different to understand and learn in a real-life dev cycle (and so dealing with other real-web-life things as well), forcing to pick random ones or to understand and choose the right framework at the wrong time (for example at beta stage, which have just happened to my team, by the way ;)

If ajax world is really so advanced to produce 134+ frameworks in one year’s time I hope that people involved will crawl soon for a set of standard or – at least – some kind of coding standard (i.e.: js behaviours via css classes vs. inline js).

My thoughts also are spinning around all that RubyOnRails excitement: coders happiness for us used to be a must, but last two php/js years made coding like a daily pain, and I think that ajax world need something kind of non-intrusive package management like Ruby gems. I suppose – and hope – dojo has something similar but it’s toooooo big to understand quickly ;)

Comment by Paolo Tresso — May 16, 2006

I generally go for whatever is most widely used; perhaps because it is generally most widely supported… and because it has already run the gauntlet of public opinion. So, I’ve been using prototype/scriptaculous for the past several months. I am, though, thinking about switching to Yahoo now that it seems like they’ve pulled in most the features and are dedicating gobs of resources to it. I REALLY like just getting the app to work well and not worrying about all the script itself.

Comment by Paul Payne — May 16, 2006

Add Google to the list. :)

Comment by Aaron — May 16, 2006

Can’t be any easier to use than this.

I don’t even think that’s even possible, strictly technically speaking.

Comment by Mikael Bergkvist — May 17, 2006

Fogbugz 5.0 released – with a little story

The two main screens in FogBugz have been ajaxified, and FogCreek has launched it as V5.0.  As usual,…

Trackback by Tim Haines — May 17, 2006

134+ Ajax Frameworks

Trackback by Kelly White — May 24, 2006

I want to use this ajax

Comment by huy — May 28, 2006

[…] 1. Dojo 2. Prototype 3. 4. Many, many, others […]

Pingback by AJAX Vs Desktop » Design Craft — July 4, 2006

135 :)

Comment by Thomas — January 24, 2007

Leave a comment

You must be logged in to post a comment.