Home >
The AJAX development community certainly has a large variety of frameworks to choose from. So, our new poll question asks which you currently prefer. I know that most AJAX developers have used more that one of these and may even have a different preference based on the project specifications. But, we are simply asking which is your overall current preference.
Although, we have compiled a list of 10 different popular AJAX frameworks for this poll, I am sure that you will tell me that we left some off. If this is the case, please post a comment to this post and we will be sure to add it to the list of choices.
Also, there is a choice of other, which you can choose and post your reason for this choice within the comments of this post.
Please note that this poll is very important to us as we are currently working on a section of InsideRIA that will be dedicated to AJAX frameworks and we are looking to the community to drive the direction of this section. Your votes will directly impact which content gets created and in what order we create it. We greatly appreciate your feedback on AJAX frameworks. Please click here to vote.
Tag Cloud
Podcasts & Screencasts
@InsideRIA on Twitter
Follow InsideRIA on Twitter
Facebook Application Development
missing qooxdoo framework
Well Spry of course ;)
This is very apples and oranges...
I'd consider JQuery, Prototype and MooTools to be in a separate category of "Common DOM/Query JS Libraries" while the others are more "Component Framework Libraries"... tho, Dojo Core definitely fits in the former.
Example... I'm currently developing a project where we chose JQuery for facilitating basic DOM access and CSS injection post-render, but are using ExtJS for various rich-component development (AJAX Grids, Forms/Fields, etc.). They play well together and both offers a strength lacking in the other.
2-cents,
Etienne
After mucking about with several (Google Web Toolkit, Dojo, JSF), I'm back to rolling my own. The underlying code doesn't change unless I change it and I don't have to try to adapt to someone else's bizarre notions of what flexible means.
I have started with Prototype/Scriptaculous, tried jQuery for a private project and i am now using mootools for everything that is possible.
I still like to work with prototype, but prototype on its own without any capabilitites to animate something is not so useful often. Scriptaculous is imho a bloated library with different solutions for similar tasks (static effect usage, instantiating of an effect, etc.). I simply do not like the way they program "pseudo-object-orientated" Javascript.
I detect mootools on my research for iPhone web-app-dev and i like it very much. Compact and powerful, well written code and a nice approach of how to write Javascript-code.
I never tried Spry, i only had a short look on it, but at the time i looked at, the examples did not impress me very much.
I have started with Prototype/Scriptaculous, tried jQuery for a private project and i am now using mootools for everything that is possible.
I still like to work with prototype, but prototype on its own without any capabilitites to animate something is not so useful. Scriptaculous is imho a bloated library with different solutions for similar tasks (static effect usage, instantiating of an effect, etc.). I simply do not like the way they program "pseudo-object-orientated" Javascript.
I detect mootools on my research for iPhone web-app-dev and i like it very much. Compact and powerful, well written code and a nice approach of how to write Javascript-code.
I never tried Spry, i only had a short look on it, but at the time i looked at, the examples did not impress me very much.