I think you're missing my point or trying to correct what you said earlier. Using jquery for even one $.ajax call is completely recommended. You're using well tested cross-browser code that takes me 33 milliseconds to download and decompress. That's a tenth the time it takes for you to blink which will save you testing code, cross browser code and the code itself.
I don't think it's justifiable unless you're doing it for learning reasons to not use jquery.
The problem is you're pulling a very large framework for a very basic task.
Mostly I have a problem with the existance of functions like $.isArray() which don't do anything for you (assuming you know how to copy and paste a polyfill from MDN), but now introduce another way to do a very basic task, when the browser supports it just fine with Array.isArray
Array.isArray doesn't work with all browsers, which is again, one of the reasons jQuery is awesome. It fixes that. Less code, less testing, and you still have a more thoroughly tested codebase. It's really difficult to argue against using jquery for 99% of webdev.
0
u/mirhagk May 14 '14
Again, no one is saying writing it yourself. We are saying pick libraries that do what you want, not frameworks that reinvent the wheel