Comments on: 134 Ajax Frameworks and Counting

By: Thomas

Thomas — Wed, 24 Jan 2007 15:02:25 +0000

135 :)

By: AJAX Vs Desktop » Design Craft

AJAX Vs Desktop » Design Craft — Tue, 04 Jul 2006 13:13:21 +0000

[...] 1. Dojo 2. Prototype 3. Script.aculo.us 4. Many, many, others [...]

By: huy

huy — Sun, 28 May 2006 10:04:16 +0000

I want to use this ajax

By: Kelly White

Kelly White — Wed, 24 May 2006 07:24:14 +0000

134+ Ajax Frameworks

By: Tim Haines

Tim Haines — Wed, 17 May 2006 21:38:19 +0000

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,…

By: Mikael Bergkvist

Mikael Bergkvist — Wed, 17 May 2006 18:04:26 +0000

Can’t be any easier to use than this.
http://www.naltabyte.se/howto.htm

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

By: Aaron

Aaron — Wed, 17 May 2006 02:04:29 +0000

Add Google to the list. :)

http://code.google.com/webtoolkit/

http://www.wiredprairie.us/journal/2006/05/google_web_toolkit_released_to.html

By: Paul Payne

Paul Payne — Tue, 16 May 2006 18:54:42 +0000

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.

By: Paolo Tresso

Paolo Tresso — Tue, 16 May 2006 17:11:42 +0000

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 ;)

By: Jason Haley

Jason Haley — Tue, 16 May 2006 14:35:58 +0000

Interesting Finds

By: ma2ã®æ—¥è¨˜

ma2ã®æ—¥è¨˜ — Tue, 16 May 2006 03:40:48 +0000

[ajax] 134 ç¨®ã®ãƒ•ãƒ¬ãƒ¼ãƒ ãƒ¯ãƒ¼ã‚¯

http://ajaxian.com/archives/134-ajax-frameworks-and-counting Ajaxé–¢é€£ã®ãƒ•ãƒ¬ãƒ¼ãƒ ãƒ¯ãƒ¼ã‚¯ã¨ãƒ©ã‚¤ãƒ–ãƒ©ãƒªã‚’èª¿ã¹ã¦ã¿ã‚‹ã¨ï¼Œ 58 in pure Javascript and another 76 with back-end support in PHP, Java, or whatever. This includes 13 for .Net, …

By: Michael Mahemoff

Michael Mahemoff — Tue, 16 May 2006 00:13:28 +0000

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.

By: Rik Arends

Rik Arends — Mon, 15 May 2006 20:41:08 +0000

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’ :)

By: Allen

Allen — Mon, 15 May 2006 17:06:48 +0000

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.