40 Comments

• Digg
• Bury

They only reason you should not be using a javascript library such as jQuery is that you might be studying. For all those in the profession you are way behind if you are just picking a javascript library now.Handy tip when combined with firebug and debugging use console.log("print this");

• Reply

• Digg
• Bury

jQuery is a really bad library to learn JavaScript with. The primary problem is that it obfuscates all the element selection.$("#mydiv").html("new content");After that command, your only reference to the #mydiv element is a hidden variable inside the jQuery object. You are forced to chain your next command, or reference the object again using $("#mydiv"). This starts getting really annoying when you try to build anything semi-complicated using object-based widgets that aren't jQuery plugins. jQuery locks you into using this confusing referencing, and one-line chaining hacks in order to do things that aren't very difficult to begin with."But.. but.. you do so much in one line of code!!!"That argument is such BS. Can you honestly say that this:$("#mydiv").html("new content").style({color:"red"});Is more concise than:var elm = dogument.getElementById("mydiv");elm.innerHTML = "new content";elm.style.color = "red";It's not, saving a few characters is not worth the effort to figure out how to do it all in one line.Have you ever tried to debug somebody's jQuery code? You can't, you have to rewrite it because the person who originally wrote it simply copy and pasted it and had no idea what was going on.

• Reply

• Digg
• Bury

It was definitely a beginner's guide... I think working with jQuery before learning the basics of javascript is okay, because if you pass the code on to someone else... at least the developer that picks it up will be familiar with the framework.

• Reply

• Digg
• Bury

Yeah, that's a typical old-school approach. Seat of the pants, jolt cola, spaghetti code until 2AM.No thanks.Javascript is a language just like any other. It's not simpler or easier. Best practices are best practices. You might like to boast about how you can understand anyone's code in 20 minutes, but I couldn't give a damn. I'm not into pissing contests, I'm into doing things right and going to bed on time.The question isn't how much code you've written, or how many other peoples' code you've expertly deciphered, but how many other people have had to maintain YOUR code, and how happy they were about it. There's absolutely nothing elitist about hating to clean up other peoples' messes. There are plenty of people out there who can code tons of functionality very quickly, but simply cannot work well in a collaborative setting.

• Reply

• Digg
• Bury

Good lord what are you talking about. Surely you have absolutely no idea what you are talking about. jQuery is a great language to learn once you know JavaScript for a billion and two reasons you should already know (if you are a good web dev). Your "primary problem" doesn't exist, only in your own head. It may not be such a bad idea for to read a few more beginner tutorials on jQuery. To say this particular arguement is BS, is to say you don't know wtf you are talking about.var elm = dogument.getElementById("mydiv");elm.innerHTML = "new content";elm.style.color = "red";Can also be done:var elm = $('#mydiv');$(elm).html('new content');$(elm).css('color','red');Ofcourse the last line should follow the second chain but was following your example in hopes you would understand it. You can then use the variable to reference the element again in the future, the same as JavaScript. So please, next time you call something bs or a hack, know what the hell you are talking about first."Have you ever tried to debug somebody's jQuery code? You can't, you have to rewrite it because the person who originally wrote it simply copy and pasted it and had no idea what was going on." -- Yea btw, you're the guy who's crap JavaScript functions I rewrite in jQuery running faster smoother and cross browser compatible eh? =] </rant>

• Reply
• 1 Reply