I like comparisons and especially when a tool takes my input and produces 3 different
Step in Compressor Rater it takes the Dojo Shrinker, JSMin and YUI compressors for Javascript and produces a report as well as gives you an option to copy paste the resulting code.
Both Jquery and Mootools are great libraries, however one must win. Is it the Cow or the Dome, find out as I compare both these libraries feature by feature.
But why now?, Mootools has just released their 1.2 version which boasts of a HashMap for clientside objects.
Jquery has seen a 1.2.1 version ( sounds familiar?, look above) for a month now.
Why dont you subscribe to the feed to be the first one to hear about it.
A while back I had this post about support for CSS3 in IE7. With a growing share of 23% and a mission to make this version automatically available to all users of Windows XP, IE7 still seems to have got it wrong for the developer.
The CSS3 frustration continues, for e.g: the “last-child” selector, could have been a boon to site designers. The trailing “class=last” that’s added to every last item of a list, the last cell of a row could have been on the way out for once and all.
The “last-child” selector is a easy way of targeting the last element of any dom node collection. This is great for any last item of a list where you dont want that seperator to appear. MS doesn’t seem to realize that just doing half baked work with “first-child” doesn’t cut it.
Mootools has a great speed test for DOM selectors in JS libraries called the “SlickSpeed” test. The results compare “Mootools “, “Prototype ” and “Jquery“. In the instance that I ran ( I only clicked “Start Tests”!) , Jquery came in first.
Jquery is on the third column in the attached thumbnail.
Its also interesting to note that “prototype” finds no results for the CSS selector (“div:nth-child(even)” and “div:nth-child(odd)”).
[tags]jquery, mootools [/tags]
Recent Comments