That and the fact that we have an amazing community who is willing to work with developers of all experience levels. In addition, we have a core team that is completely accessible and willing to interact with the jQuery community. Essentially, we go to great lengths to:

1) Listen to the jQuery community
2) Provide as many resources as possible to get valuable information out to jQuery developers
3) Ensure that everyone on the team is accessible and respectful
4) continue to evolve jQuery to meet the needs of the community

Unlike other projects, we are out in the community trying to help out and it's one of our core priorities, not an after-thought.

Rey...
jQuery Team

kiusau wrote:
jQuery outperforms Prototype by leaps and bounds.  Surely this is an
important reason for jQuery's increasingly popularity over Prototype.
Thanks for the great reference!

Roddy

On May 21, 1:02 pm, Jackson Ferreira de Andrade Mafra
<jacksonf...@gmail.com> wrote:
http://blog.creonfx.com/examples/javascript/speed-compersion-raw-data...http://blog.creonfx.com/javascript/mootools-vs-jquery-vs-prototype-vs...

att.
(ツ)
Jackson F. de A. Mafra
Designer,Desenvolvedor e Consultorhttp://www.jacksonfdam.com.br

Esta mensagem, incluindo seus anexos, pode conter informações confidenciais
e/ou privilegiadas. Se você não for a pessoa autorizada a receber esta
mensagem, não pode usar, copiar ou divulgar as informações nela contidas ou
tomar qualquer ação baseada nessas informações. Caso esta mensagem tenha
sido recebida por engano, por favor avise imediatamente o remetente,
respondendo o e-mail e em seguida elimine-a do seu sistema. Agradeço sua
cooperação.

On Thu, May 21, 2009 at 5:00 PM, Matt Kruse <m...@thekrusefamily.com> wrote:

All 3 frameworks have pros and cons. They have many technical
similarities and each come with their own set of problems. If you can
avoid using a framework, always do that. But if the pros of using a
framework outweigh the cons, I think the decision mostly comes down to
popularity.
Choose the framework that will have the most documentation, the
biggest user community, will be around the longest, will have the most
number of developers familiar with it, and can be seen as gaining in
popularity rather than declining.
If you look at Google Trends to compare the three:
http://www.google.com/trends?q=jquery+javascript%2Cmootools+javascrip...
you'll see that MooTools and Prototype are steady or declining, while
jQuery has a dominant lead in popularity and is increasing rapidly.
Granted, this is only an analysis of searches, but it's a fair picture
of relative popularity of the different frameworks. There is always
some safety in choosing the "market leader" and if you are going in
blind with no desire to do an in-depth analysis of each option, then
choosing jQuery would probably be your safest best.
IMO,
Matt Kruse
On May 21, 2:05 pm, kiusau <kiu...@mac.com> wrote:
After a badly needed pause of some length, my need for sophisticated
JavaScript has reemerged.  During my departure I have discovered two
other similar JavaScript modules called MooTools and Prototype.  With
my reemergence I have also realized that all of these require a
certain amount of commitment that goes beyond what I initially
anticipated.  What I would like from you all is a convincing argument
to remain that is based on the following comparison:
1) What are the principal advantages of jQuery over Prototype and
MooTools?
2) What are the principal disadvantages of jQuery when compared with
Protoype and MooTools?
Roddy

Reply via email to