Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@d3vcho main reason for me: jQuery can't handle shadow dom well.
also, IE compatibility got less important.
And some ideological reasons, which are obviously not important -
plus, 80+kb for jQuery is in many cases just too much to justify...
also, you don't learn JS, you learn jQuery, which will fuck you up at some point -
d3vcho2708y@tambo Actually I'm learning both, some of the online courses I'm at, include JavaScript and jQuery
-
The most important thing is to learn where to use one or the other. I've seen top many examples over the years of people using jQuery unnecessarily when js would have been fine. Don't add unnecessary overhead to your project.
-
I actually prefer using Vanilla JS whenever I can. Agreed that it's a little more verbose, but it's still more efficient than including a library for just 1-2 functions slowing down load time. Also, most developers who start with jQuery become completely dependent on it, since it's really non intuitive to have an if else statement than to have a toggle class. I think that's also harmful since jQuery is becoming almost absolute.
-
I'd say that jQuery is used on a vast majority of sites, so being familiar with it is almost a necessity. I agree with all the common complaints: it's large if you're only using one or two things, IE is up to speed (kinda) so it's not as necessary, it can add overhead when vanilla js works just as well, among others. That said, look at job postings. There's a ton out there with jQuery experience either necessary or a plus. Knowing it can get your foot in a lot of doors.
I'm starting to go deeper with JavaScript and jQuery. What do you think of jQuery? Any advices or recommendations?
undefined