3 ms·
The second part of that line was referring to javascript in general as compared to other languages. And I think you are insane :) I've never met a single devel
by tkahn6 16y ago
The second part of that line was referring to javascript in general as compared to other languages.
And I think you are insane :)
I've never met a single developer (besides you apparently) who prefers the tedium of raw javascript DOM manipulation to jQuery's abstracted methodology.
I'll take
var i = $('.someclass:first').next().val()
over the equivalent raw javascript any day of the week.
- axod 16y agoThere's a lot of us about ;) That syntax you quote is not something I like, and isn't something that will run fast on browsers either. $('<code>') is quite ugly. Any typos inside that string won't be caught. Also I don't find chaining to improve code readability. Dealing with the DOM directly means you can optimize properly. For example, say you want to get an input elements value, in js you'd do: theInputElement.value Since you probably created or referenced the input element from js earlier and saved a ref to it...
- tkahn6 16y agoIf it works for you, more power to you. :)
- thaumaturgy 16y ago> I've never met a single developer (besides you apparently)... Well, now you have. We're just not as noisy as the jQuery guys. :-)