Live data from Hacker News

You Don't Need JQuery

blog.garstasio.com

171–180 of 201 posts

Re: You Don't Need JQuery

#171
Except, being old school, I remember 7 or 8 years ago, when everyone would complain about IE compatibility and various quirks between browsers. JQuery apparently sorted all of that out. And now we should go back to the bad old ways?

Re: You Don't Need JQuery

#172
post #66

Earlier quoted context omitted.

Surely you can expand on this story. What made using jQuery so painful?

I'll try. My client was mad I was trying to charge him an extra $6000 for the time I spend to get the stuff I write to work across different browsers and asked me to use jQuery instead.

[deleted]

Re: You Don't Need JQuery

#173

Articles like this make me thankful that I've done my 10,000 hours of web development learning the ins and outs of the DOM and it's interactions with JavaScript (mostly topics covered in Crockford's book). Admittedly, about 9,950 of those hours were making it work in IE6. jQuery is a framework, like many others. Programming is not about learning frameworks, it's about learning the language, it's runtime behaviours an…

after 10,000 hours you're still calling jQuery a framework?

Re: You Don't Need JQuery

#176

Earlier quoted context omitted.

Yes, why use a tried and tested tool that can be incorporated into your site and served efficiently with just a single extra line, when instead you could make building your site more complicated than compiling an entire Linux distribution from source, spend days choosing between a bunch of almost identical micro-libraries for every little thing you need to do, and lock yourself into a proprietary framework that will…

make building your site more complicated than compiling an entire Linux distribution from source http://browserify.org/ Browserify is not at all complicated. spend days choosing between a bunch of almost identical micro-libraries for every little thing you need to do Just search npm and pick the one that is being used the most. lock yourself into a proprietary framework that will be considered legacy code as soon as…

I don't like how browserify will only ever work by serving combined files. Granted it has source maps but it's still terrible that you just can't debug your app with individual files with it. Neither do I assume setting breakpoints works very well in it?

Re: You Don't Need JQuery

#177
Everytime I see one of these I think I should do more with https://news.ycombinator.com/item?id=7863271

Yes it's useful to know what jQuery is doing underneath but the whole point of it is that you don't have to worry about that and can concentrate on on the rest of your build.

Sure, you might not need it and there are other alternatives, both as plain JS and with other libraries, but it does it's job well and will always be easier for others to pick up when coming onto a project.

Re: You Don't Need JQuery

#178
Of course you don't need jQuery, if your customers are happy that you target only one browser specific version.

I think the rest of us will rather keep on using it, or similar library.

Re: You Don't Need JQuery

#179
post #8

Every time I try to build something without jQuery, I regret it. Not because of selectors, that's (sometimes) easy to do for lots of (basic) selectors. Not because of DOM manipulation, as long as you're willing to sacrifice simplicity and readability, you can build iterative loops to modify a collection of HTML elements. No, it's the unexpected things that cause me pain. Want to use event handlers on dynamically gene…

Yep. Use the built in browser methods? For which browser?!? All of them? I have to support some enterprise guys on IE8, sometimes I'm lucky to have them on IE9. Life isn't always a hipster website where people can get lunch delivered on their phone or whatever. Things like jQuery are fine.

Fully agree with you, it is worse actually as even between versions of a specific browser, behaviors change.
Post reply on HN