5 ms·
JQuery 1.5.1 released, includes full IE 9 support
- arkitaip 16y agoI am incredibly thankful that jQuery exists. The other day I had to code some basic javascript in a environment where embedding jQuery wasn't an option (too much overhead) - boy what a PITA. Basic stuff like writing selectors took forever and I had to resolve to "low level" coding. What would have taken a couple of seconds in jQuery took several hours of research, and trial and error. I planned on adding a basic fading/sliding effect - forget about it. Takes to much time in ordinary javascript. So thanks John Resig and the rest of the jQuery dev team for making us web dev guys more productive and actually making JavaScript fun.
- albertsun 16y agoOn the other hand... congrats! Now you know more about the inner-workings of jQuery and are a better javascript programmer.
- abp 16y agoQuestion is for how long. I've written several thousand lines of native, cross-browser javascript some years ago and from time to time again. But i don't remember a lot of the workarounds, from the top of my head. Fiddling with cross-browser support is something that my brain don't like to keep today, be it js or css. Things like jQuery for js and compass for css come in handy to brush over that. :)
- dualogy 16y agojQuery too much overhead? What kind of environment was that?
- bzbarsky 16y agoPretty much any environment where you care about performance of your code, actually. A lot of the simple-looking jquery stuff is implemented with tons of indirection, branching, etc. Just compare the work a browser has to do for something like: document.getElementById("foo").setAttribute("bar", "baz"); to the work needed for the jquery equivalent... Now the good thing is that most consumers of jquery don't care about performance of their code (in that they're doing small enough amounts of stuff it doesn't matter much).
- rorrr 16y agoOut of curiousity I tested that particular statement, and you're right. Compared to $('#foo').attr('bar', 'baz'); your code is 30 times faster in Chrome 9 81 times faster in Firefox 3.6
- tropin 16y agoCould you share your test code?
- ams6110 16y agoIn most cases, though, using jquery to do something like adding a class, or setting a value, is still plenty fast enough. We're talking about code that runs in the browser, where things move on human timescales. Don't optimize prematurely.
- bzbarsky 16y agoThe problems start when you add a class to 10,000 elements on the page. And yes, I've seen pages doing this with jquery where the jquery overhead was what made the difference between a 20ms operation (not user-perceptible) and a 1s operation (very much user-perceptible).
- mazuhl 16y ago47 times faster in Firefox 3.6.1 7 times faster in IE 8
- rimantas 16y ago> Now the good thing is that most consumers of jquery don't > care about performance of their code Many do, but more do care about cross-browser compatibility and when you need to support IE6,7 home-rolled code is not likely to cut all the research and effort that's embedded in jQuery.
- bradgessler 16y agoBookmarklets
- JonnieCache 16y agoRemember that jQuery's selectors can be used separately: they're a wrapper around the Sizzle library. It's 5kb after minification and gzip. http://sizzlejs.com/ http://sizzlejs.com/ Can't speak to the performance relative to JQuery or to raw javascript however.
- professortodd 16y agoI know that the javascript purists don't like jquery, but I'm a big fan.
- jherdman 16y agoReally? Why ever not? What do they prefer?
- r00fus 16y agoSomething lighter than 238kb. I remember when jquery first came out, and ExtJS was around that size (actually a bit larger) and one of the big popularity factors of jQuery was a much smaller library size. Also some places like Apple have their own internal js frameworks and want folks who know and can code bare-metal js.
- krakensden 16y agoThere's Zepto.js. For desktop browsers, use the Google CDN and your users probably won't download a thing. And for free, you get sane DOM interaction, and an enormous body of work papering over the differences between browsers.
- trezor 16y agoFor desktop browsers, use the Google CDN and your users probably won't download a thing. And Google is one step closer to tracking everything everyone does on every website. As if now forcing people to deploy Google Analytics on their websites if they want keyword data from Google wasn't enough, do we really want to help and encourage Google to get in a position where they effectively control the entire internet? One company controls over 90% of internet search and referral and they actually have the power to kill any company they don't like. Right now they may be behaving, but what if some competitor comes along which is showing some edge? Can we trust Google to do the right thing? Google also hosts files needed by a majority of websites. They also withhold information from you about you and your site and force you to register an account with them and deploy their software on your sites to get access to a subset of that information. And you are encouraging people to help that company get a stronger grip. For what benefit? At what cost? Sorry for not being a fanboy, but try looking at the bigger picture here. Would you be OK with one company controlling the entire Internet if that company was Apple? If it was Microsoft? Hosting your own 23kb jQuery file does not cost that much. Actually practically nothing. Not in terms of bandwidth and neither in terms of perceived performance. Unless you are hosting your website on a 36.6kbps modem, host your own. Do the web some good.
- jcr 16y agoI really do realize computer systems and software are primarily designed for normal people rather than the disabled. I also understand the vastly competitive world of web development and the advantages of having a cool looking, feature rich site. None the less, I take offense to the part of jquery-ui that is hijacking the web browser UI. It is remapping keys and pointer usage (text selection). This should have never been allowed in the W3C and EMACscript (javascript) standards. Hijacking the browser UI of a disabled person is like kicking the crutches out from under someone just to see them fall and because you think it will make you look cool to others. Web developers never know how a user-agent is configured and never know the needs of the person using the web browser. Changing how the UI normally works really does hurt, confuse and infuriate many people, and probably more than just the disabled folks. Sure, disabled people are a very small part of the population, and they typically are not the rich consumers buying the latest and greatest. They may not be your target market, your real customer concern, but excluding them with browser hijacking is unnecessary, and in some ways unfair. At least please think over...
- rhizome 16y agoYou're right on many points, of course, but hyperboles of cruelty like "kicking the crutches out...just to see them fall and...you think it will make you look cool" don't seem to be grounded in reality.
- jcr 16y agoYour criticism is fair, and I should have written something better. I won't edit the original and I'll stand by my mistake since it would make your comment seem off. The thing to realize is I was REALLY trying to contain my temper when the hyperbole slipped out. It's tough be positive while share a perspective of frustration few developers ever see.
- arkitaip 16y agoNot sure that jQuery deserves to be blamed for shoddy interface coding. Any competent web developer knows that you always start out by designing your interfaces so that they work with scripts and plugins disabled [1]. If some - ok, most - devs choose to ignore this design principle then jQuery is hardly to blame. [1] Obviously there are situations when it simply isn't possible to create fully accessible solutions. Sometimes our hands are tied by management, tech stack requirements, etc.