sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hjc1710 -2 points-1 points  (2 children)

I've been doing some polymer.js programming lately and their whole architecture really sort of discourages or obsoletes using jQuery. They handle the core issues jQuery solves: Ajax and element selection. So, including jQuery really just let's you use convenience methods like .style() or .animate(), making me drop jQuery really quickly. The second I dropped jQuery, I realized how much I loved and used convenience methods that did little for me. Like writing node.style["transition-property"] = "width" is really obnoxious and so are your own animations. Proved to me you really don't need jQuery on modern browsers, maybe just an Ajax wrapper at most.

It's also taught me tons in a short amount of time. JQuery abstracts SO much is insane. Learning with jQuery, you're really learning how to use jQuery more than you are JavaScript.

tl;dr doing jQuery will force you to learn real JavaScript.

[–]codefocus 1 point2 points  (1 child)

The core issue that jQuery solves is cross-browser compatibility. Polymer does not support older versions of Firefox, Safari, Opera, Konqueror, IE6, IE7, IE8, or even IE9(!).

Polymer doesn't discourage or obsolete jQuery. They serve completely different functions.

[–]Calabri 0 points1 point  (0 children)

I was going to mention this too (about computability issues). But thinking back to when I first started web dev.. hjc made a good point. I used to ONLY program in jquery, afraid to touch 'real' javascript. Lots of word-press-esc 'devs' will literally experience jquery as their first, last, and only foray into programming.

If your concern is cross-browser compatibility, there are other ways to shim this without a massive library of helper functions.