StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>jQuery is very similar in terms of what it offers to MooTools, while very different in how it offers those things. MooTools is very explicit and requires a deeper understanding of how some things work under the hood, while jQuery hides that complexity away. Hiding complexity follows the 80-20 principle in my opinion, and when the abstraction leaks 20% of the times, understanding the inner workings becomes important.</p> <p>Having a good grasp of MooTools in and out should make it very easy for you to pickup jQuery. Some examples of this explicit behavior would be how jQuery wraps single and multiple elements under the <code>$</code> umbrella, while MooTools provides an explicit interface for both with <code>$</code> and <code>$$</code>.</p> <p>When making AJAX calls for one's own domain or external domains using JSONP, jQuery routes everything through the <code>$.ajax</code> function, while MooTools again has separate interfaces for those in <code>Request</code> and <code>Request.JSONP</code>.</p> <p>Neither approach is good or bad, but re-using the same interfaces that most are already familiar with reduces the learning curve.</p> <p>Some good resources for diving deep into jQuery would be,</p> <ul> <li>John Resig's <a href="http://ejohn.org/category/blog/" rel="nofollow noreferrer">blog</a></li> <li>jQuery's official <a href="http://blog.jquery.com/" rel="nofollow noreferrer">blog</a></li> <li><a href="http://loft.bocoup.com/john-resig-advanced-jquery/" rel="nofollow noreferrer">Video</a> presentation on advanced jQuery concepts.</li> <li><a href="https://stackoverflow.com/tags/jquery/hot?filter=all">Hottest</a> jQuery answers on StackOverflow</li> </ul> <p>With respect to code organization, most code written for jQuery is very different to MooTools. While MooTools uses a very classical style using <em>classes</em>, and <em>objects</em>, jQuery code is mostly very DOM-centric. So even with custom plugins, you'll be attaching data to DOM elements. To see some almost real-life examples of a DOM-centric approach, you can watch the video linked in this <a href="https://stackoverflow.com/questions/5905994/i-know-its-bad-to-store-data-in-the-dom-but-why/5906142#5906142">answer</a>.</p> <p>I wouldn't worry much about selector engine performance as that's mostly a red-herring unless you are writing Excel for the web or something.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload