What is JQuery performance compared to YUI, Dojo and other frameworks?

Question

I have been using JQuery for quite sometime now and I'm pretty much happy with the performance.

I'm just wondering if there is any performance comparison between jQuery, YUI, Dojo, Prototype, Mootools etc.? What are all the advantages of using jQuery framework over others?

Answer 1

For your review:

• jQuery vs Prototype vs MooTools 2008
• jQuery vs MooTools vs Prototype vs YUI vs Dojo 2009
• jQuery vs MooTools 2010

If it's possible, build a set of atomic tasks that are common in your applications. Model each task in the frameworks you're interested in and benchmark. Benchmarks are notoriously finicky so you're better off benchmarking your exact use cases.

One seldom uttered advantage to jQuery is John Resig. He's a real role model, very appealing in so many ways. His taste is impeccable.

Answer 2

This is kind of like asking if cars are faster than trucks. These libraries are made up of dozens or hundreds of methods. I expect you will find that each library is faster for some activities, slower in others, and the same on quite a few.

All in all, I'd decide on a library based on features not performance.

Answer 3

All in all I see many correct answers here, however, rather than just reference performance inquiries, or just look for features, I have another theory.

A few things to consider (as I did beforeofficially setting jQuery as the Lib I use at work and home):

1. Industry standards: Simply put, what is going to be the most versatile among multiple platforms as well as, what looks like it will continue to grow with the industry.
   • In my opinion this more important than any other factor as this will help determine both the life of your web-app/sight and the extensability
   • It's been my find (through personal research, not gonna list the things I looked at and did as it would get lengthy) that jQuery best meets these qualifications, however, you might look at what you want your sight/app to do and see how those features are used on multiple platforms to best determine if this is the same measure for yourself.
2. Almost forget(edited in) SECURITY!!! I didn't see too many people mention this, but something to think about. For instance, Prototype tends to be faster than jQuery, especially in ajax calls, however, this is because jQuery does MUCH more behind the seens to ensure the "security" of you ajax call as well as giving you all the tools you need to set these securities manually, where as Prototype does very little behind the scene work and expects you to use their class system to create your own security measures on ajax calls. This is the definitive number 2 thing to look for in js libs as js hacks are some of the most widely used at this time!
3. In my personal opinion, feature richness is just slightly ahead of performance, because, while a lib may lack in performance, what it offers in features will (if it's a good lib) continually be updated to improve its performance. Thus making feature richness more important.
   • as a sub-conclusion here, also look at ease of use in these features. One thing I tend to like about jQuery over some of the others is its repetitive use in "styleing" of the code. They are very forcful with how plugins are writtin for their lib thus making everything easily importable and useful in that I dont have to learn new mark up to understand a plugin. This is VERY important to me.
4. Finally, performance, performance is important, however, as mentioned before, many lacking items of performance can be made up for by an easy to use mark up combined with feature-richness combined with proven growth. Alot of recent(3yrs old still, but compares alot of known types) information about performance can be found here.

All in all, these are just my opinions, but some things to consider when deciding on a new change in code. One last thing I didn't mention, how easy will it be to convert your code? If you've already used jQuery for a while, then you've prolly already made so much use of its "easy" features, that, at this point, a code change could set you back weeks or even months. My personal suggestion would be to "go with what you know" but at the same time, to maybe, as a side project, study something else you are interested in until you have a grasp enough on it to make that final decision and possible change.

Answer 4

All javascript framework never give better performance then others in Every function they implemented in framework so they never compare them.

if you want to performance comparison between jQuery 's it's own version then you should read jQuery blog to know about them.

Answer 5

From a performance perspective I don't think there is a lot of difference (gut feeling)

From a usage perspective it is what you are used to and you can learn any of them (although for jQuery the number of resources seems larger)

The big difference for me at the moment is how much Microsoft is pushing. Microsoft supplies jQuery with their visual studio distributions, gives support and contributes to jQuery.

Answer 6

I think you would also want to consider what other frameworks you might be working in and what libraries they leverage. For example, WordPress already relies quite heavily on jQuery, already loads the library, and has some built-in interoperability functions in PHP that facilitate uitlizing jQuery within your own WordPress-based development. On the other hand, Joomla bundles MooTools, so if you're working in that environment, you're better off leveraging that library instead (particularly since both libraries hijack '$' so you have to do some namespacing protection if you're going to use them both).

Otherwise, you need to balance: 1. benchmark performance 2. feature set 3. developer community and plugin / resource availability 4. API ease of use 5. documentation

Not necessarily in that order.

Based on that, MooTools and jQuery stand out for me as the two major contenders, with MooTools possibly winning out on performance and jQuery on resources.