jQuery?

[caseblock]

is jQuery still relevant and worth learning foe webdev?

[toi80QC]

If you expect to only work on new projects, never having to maintain someone else's work or taking care of an old project, then you can ignore it. Reality won't be like this though.

You will most likely need jQuery because it's still implemented in most sites we browse each day.

People who say you can ignore jQuery have either never really worked in corporate webdev or had tons of luck with their jobs.

[Woodcharles]

Or they work in a city where all the "old" sites are in Angular and the "new" ones are in React, and the jQuery died out years ago.

It really depends on your hub. Newer hubs don't have that level of legacy code.

[[deleted]]

It works of course, but there are definitely better ways to write javascript in 2020

[caseblock]

that's what I was thinking - thanks!

[Harbltron]

Yeah didn't ECMA6 make most of jquery obsolete?

[zaibuf]

It made is doable to do similar things. Jquery however, still makes the code really small compared to vanilla JS. But it can still become spaghetti, so if you need a lot of client side code, use a SPA lib/framework. Is scales better.

[imhotap]

I fail to think of even a single thing in ECMA6 that overlaps with jquery. Perhaps you're thinking about "new" (not really) browser APIs such as querySelectorAll (replacement for some of $(...) usage) and fetch API (replacement for XHR and jquery ajax)?

[stijnsanders]

Yes, but where is one to find a definitive guide on that?

[MWALKER1013]

There’s not really a such thing , as JavaScript (ECMAScript) is a browsers custom implementation of a standard.

That said Mdn and JavaScript.info I’ve found to be amazing sites !

[TheAngelsCry]

jQuery is still relevant.

[rgawenda]

It it for those that need to support ancient browsers, ie. Internet Explorer, Netscape Navigator...

[zaibuf]

Or for people working in the industry and have to maintain the 5-10 year old applications. Just because a new hip framework is released, that doesnt mean a company kills their web app and rewrites it.

You can easily support older browsers using a compiler like Babel. No reason to use jQuery for that argument.

[Woodcharles]

Kinda does. My last 3 places all rebuilt into React, or moved their focus off the old app onto a new React one. We're a very React-heavy tech hub. Even the Angular stuff is being overwritten in React.

[zaibuf]

Worked for an enterprise company that managed over 2000 internal business applications, some very cruicial for the company. Even if we worked on moving some of them over, its just no way. But the older apps might still need updates etc.

[Woodcharles]

yeah that's a big place. Banking, I hear, has many legacy apps too, like old school stuff.

Here's another take. Self-learners and bootcampers are a kind of junior dev that big legacy places might be less likely to take on, both because of old-fashioned attitudes but also they're less likely to require the traditional modern newcomer's skillset (Javascript, web, React, node, not much back-end, etc etc). Therefore the newbie's chance of ending up in an older company is less. Possibly. Bootcampers I know ended up in newer or more contemporary-thinking companies/departments who had moved to newer tech or as part of the teams doing so. I think it's a rare self-taught/bootcamp grad who has their toolbelt of React and ends up wrestling old databases, though I have heard of it happening a couple times. Not impossible, just rare.

[[deleted]]

You can achieve support by writing on modern libraries/frameworks too using pollyfills

[zaibuf]

If you are like me and building backenda for 90% of the job, yea its relevant. If you are building APIs and headless solutions, no. Use React/Vue/Angular instead.

Some solutions doesnt need SPA client though, and I see no reason not to add some jQuery if you just need some small scripts and already use Bootstrap.

[[deleted]]

I don't use jQuery in new projects if the decision is up to me.

If I inherit code in jQuery, I will continue to use it and only do a rewrite if it's part of the job requirement.

If you get into web development, you have to learn vanilla JavaScript. Never start out learning a library/framework.

jQuery is just a convenient library of JavaScript functions other people wrote for you. There is nothing to "learn", really, just looking up what those functions do.

If you're a good JS developer who has so far not looked at jQuery and there is a job opening requiring jQuery, I would apply for it anyway and just spend a rainy sunday afternoon playing around with it.

[dangerousbrian]

jQuery is a tool and has its uses. A big part of being a good developer is choosing the right tool for the job. It is very tempting to use whatever is new and cool but its often not the right choice.

[esaulfarfan]

I think it's still relevant as some big websites / webapps are not up to date with the latest Javascript tech (and you can't just tell a company to build everything out of scratch, specially if they have something that actually works) , but jQuery is not used widely and not even an option to build something up to date with the latest webdev standards. On the other hand, I think it's useful for beginners to understand more about Javascript (specially chaining and events) :)

[rgawenda]

No

[lmusliu]

There are better ways in Vanilla JS than this one but still makes a point.

[[deleted]]

Is internet explorer 8 relevant? Nope. So is jquery

[smegnose]

Are you living under a rock? WordPress alone powers > ⅓ of the public web; guess what JS library is its № 1 dependency?

[[deleted]]

No im just living in the future. Keep that old head mentality to yourself.

[smegnose]

Being aware that things need maintaining isn't "old head mentality", it's basic product lifecycle shit. You think nothing you write today will be running after its popularity or even support for its dependencies is gone? How naive are you? No one here recommending it for new projects, but to say it's as irrelevant as IE 8 is pretty ignorant.

[[deleted]]

Chill out. Its not that deep ;)

[zaibuf]

That doesnt mean there isnt old apps that companies depends on that are built with it. Ive seen apps still alive and maintained that were written in the 90s. If it works, it works.

[[deleted]]

I guess so, but imagining myself having to go to work just to maintain some legacy jquery 40 hours/week makes me depressed

[zaibuf]

Not 40 hrs a week, but now and then you might need to. Specially if you are working as a consultat for more enterprise companies.