I don't like the addition instruction "jQuery fixes a lot of cross-browser issues." This is somewhat misleading, as, first of all, what jQuery does is eliminating many of the cross browser issues related to the DOM . For me, a big problem in web development is CSS cross-browser issues, as they cannot be simply encoded. With CSS, we pretty much hung up on what we got (and, unfortunately, this is much less than even simple Javascript).
Of course, there are Javascript libraries that actively change styles in the browser, trying to achieve greater consistency, but I find such methods ugly. Filling in cross-browser logic in Javascript functions is a child game compared to even achieving similar page layout results between IE and ... everything else using pure CSS.
Honestly, whenever I write code for a single browser or ... not IE, I usually don't use jQuery. Defining a few simple wrapper functions around document.getElementById/getElementsByTagName/evaluate can often provide almost jQuery brevity with no overhead. In fact, without confusing the cross-browser BS that you need to deal with, hacking helper functions as needed is a painless and almost enjoyable task, especially if you give up any restrictions on expanding Javasciprt / DOM built-in objects.
But if you are really looking for situations where jQuery is completely useless, try writing server-side Javascript. No DOM, no CSS, no IE, just Javascript bliss. Ah Node.js , where you have been all my life.
source share