jQuery vs Dojo Toolkit vs Prototype vs MooTools

This is a very quick, unthorough rundown of the most popular Javascript frameworks at the time, and why I currently favor jQuery.

I did not make a significant time investment in my investigation, but there were a couple of factors I was interested in:

  • I wanted a framework that did not include a faux class-based object framework. Javascript is prototype based and very powerful that way. (I'll write my Javascript in Javascript, thank you.)
  • I wanted a framework that imposed minimal littering of the current window's global namespace.
  • I wanted a framework that was simple to learn and easy to use.

jQuery best fit the bill. There are no false classes in jQuery; it leaves coding style up to you (not so in Prototype or MooTools). In jQuery, there is minimal littering of the global namespace -- the only exported symbols are jQuery and the optional $. (Again, this is not the case with Prototype and MooTools.) Lastly, jQuery wins hands down on ease of use. You could pick it up in five minutes if you are a seasoned web developer. The Dojo Toolkit looks promising -- I especially like its module packaging framework -- but it will require a more significant time investment than the elegant jQuery.

Here's a closing thought: I would like to see an entirely independent module packaging framework for Javascript. Anyone know of one?

I'm sure that this post will be controversial to some of you MooTools and Prototype zealots. Tell me why I'm wrong! I'd love to hear your take.


0 comments :: jQuery vs Dojo Toolkit vs Prototype vs MooTools

Post a Comment