Debate: Prototype vs. jQuery
Along the way, though, I’ve been hearing an increasingly strong chorus in favor of jQuery. I had taken a cursory look at jQuery and was impressed, but didn’t see anything compelling enough to make me switch. But increasingly the voices favoring jQuery have included people I really respect, including (over the past few months) several of my colleagues here at Relevance.
He goes on giving a detailed list of pros and cons and leans towards Prototype:
I don’t think this makes a slam-dunk case for Prototype over jQuery. And certainly jQuery could improve; its design is not fundamentally limited. (For that matter, many of what I consider the missing pieces in jQuery are available as plugins.) It’s unfortunate that some of jQuery’s API flaws can’t be fixed without breaking compatibility, but in a future version even that may be an option.
Ultimately, I didn't find Glenn's argument to be convincing, although some of the commenters were happy to hear that they could feel good about remaining ignorant about jQuery. jQuery, being the later library, had the benefit of learning from Prototype's trials, coming up with a wonderfully expressive programming model. But mistakes were made, and jQuery's sudden popularity makes it seemingly impossible to correct those mistakes. Apparently the jQuery community forgives them. Glenn does not. John Resig is also a smart guy, and I imagine that he is frustrated at being knocked for his mistakes while being unable to repair them. Perhaps now he knows how Brendan feels.
Dion Almaer from Mozilla disagrees and finds Prototype closer to his taste:
These days, without any real context (e.g. skills on the team, what the project does) I kinda think:
- jQuery is fantastic for taking a website and making it dynamic. Easy. elegant. Beautiful. If I was a designer doing a rich site I would stop here.
Prototype, for me, fits in between these worlds. It is small enough to feel small (not a huge library to learn) yet large enough that I don’t jump out into creating a lot of my own code.
So, which do you think is the best Ajax framework around?
OO vs Functional?
I used JQuery in early stage of a large intranet application, but meanwhile I switched to ExtJs of it's very clean extendible modelling and widget creation modelling behavior. JQuery is rather a rich GUI tool dispite ExtJs it is more enterprise ready. Though I don't have any experience with prototype and looking through only the documentation I think it's closer to ExtJs than JQuery is.
I found JQuery convenient to get richer ui (fast) on the site but came accross incompatibility using different plugin versions. While ExtJs is ready to use components are different to handle but the consistent usability of them become familiar after a while and is faster in many things like building grids,pages or windows like layout.
Adoption is also important
You probably mean Prototype.
This discussion and more at JSConf 2009
Craig Motlin Sep 01, 2014