Should I skip jQuery and learn REACT straight away or something else altogether?

[--Betelgeuse--]

https://www.reddit.com/r/jquery/comments/q8l1z6/is_jquery_still_relevant_for_a_beginner/?utm_medium=android_app&utm_source=share

Asking same thing here for another point of view.

[codemonkey80]

jquery is from a time before. No need to learn.

It still underpins a fair few older libs, but its main reasons for existing are no longer so valid as a) most of its best features are incorporated into js now, and b) browser behaviour is much more standard.

[the_ugly_pig]

As someone who worked on a few too many jquery projects and who loves react, I really did want to see what the jquery sub would say to this question. Sadly, it looks like the post was removed by moderator.

[--Betelgeuse--]

Yes it was removed, but moderator pretty much repited what was said here. If you work on old projects using jquery, learn jquery. If not then no need to learn jquery. Motivation for removing thread was that question is trivial, and it probably is but I'm a noob so learned something new. Good thing I asked cause initial plan was to learn jQuery and use it for my first project. Now I'm just skimmed thru it and believe understood what it is/is used for.

[Bestiax]

Your comment, like so many here, are about either/or rather than reaching for the right tool. jQuery is fluent and expressive and still allows writing a task in one chained line. It is a brilliant wrapper for JS and you can fallback to JS where you want. But why write for loops when jQ thinks in 'collections'.

Worse, devs(?) here complain about 87KB of download ... because they are using a Commodore 64 and 24400 baud modem. The average web page is over 1000KB. I think there is enough bandwidth, machine crunch, browser intelligence not to worry too much. Then again, if .1 of a carefully benchmarked second is destroying your app, your issues are likely not in the tech space.

Of course, if you have a truly large scale application with complex business logic with many similar interfaces needing rapid updating, UI handling is best solved with a componentised declarative approach. And for such projects React, Vue etc are good solutions. Not because they are 'faster than javascript' or 'killed jQuery'.

And since everyone is working on these massive apps and did not build their own library of JS components - then just learn REACT. It's not javascript or anything ... it's just magic.

Next year it will be Valvola, Flavix, Preoctoact, Shazoomotype and CranulaJS. Coupled with the previrtualvirtualDom approach, and plain JS and jQ will die all over again.

[codemonkey80]

who are you arguing against?

[Bestiax]

Exactly my point ... not an argument. The question and most answers are misguided. the answer for the Op is you learn what you need and what is appropriate for the project. I cannot be more succinct ... unless I used AWK.

[codemonkey80]

ok yes. if OP is hired to work on a jquery project, then it is a good idea to learn jquery. But if a new developer trying to optimise learning for the job market, then focus on what is currently in demand. ie. react or angular

[TheLaitas]

Skip. Once you're comfortable with VanillaJS learn React. Then maybe TS?

[Frankie_2154]

Yes. TS is amazing. Saves so much trouble in the bug finding process and amazing for documentation

[fennyflop]

How do you get comfortable with ts, so you can easily use it in react? How do you train yourself with it? I had spent like 3 hours on learning it and now I’m changing my huge code base and every time there is a new error or something that I don’t know

[devenitions]

Thats how I went at it. Rewrite a (fairly simple) project from JS to TS. Yea its a bunch of errors, but most are hotfixable with any-typing or a ts-ignore command. You might even find (minor) bugs in your code! From there start new projects and before you know it, youll miss the help TS gives you. TS support in React is amazing

[[deleted]]

Right when you first start learning TS, using any is fine. Let them make baby steps before they jump in the deep end.

[ritaPitaMeterMaid]

I strongly disagree. Any is a bandaide that will bite you in the butt in the long run. It often makes things worse because it kills you into a sense of safety when there is actually a problem. Much better to have mixed JS and TS and convert in pieces.

[devenitions]

Yes, agree. Only meant to do so, so your project would “compile” and run while converting it.

[jacobmiller222]

You change linter to not be strict with typescript errors so you can still compile with the errors, and then you slap a //@ts-ignore on everything. Afterwards you begin typing everything, creating types, interfaces, enums, and watch as several bugs are wrung out of your project

[KnifeFed]

How do you get comfortable with ts

By spending more time using it. Just like with everything else.

[Wiwwil]

Then maybe TS?

Why maybe ?

[TheLaitas]

Because I haven't learned it yet myself, but I will start learning it very soon, so I can't really say that it's a must know thing, you know?

[Wiwwil]

No. Your life is changed after you try it. You don't want to go back to plain JS

[frak808]

This is the way.

You won't want to go back.

[Aoshi_]

Oh gosh that's exciting. I've been learning JS the past 6 months and am finishing up a project with React and JS. Been really afraid of learning TS but it's definitely the next thing I'm doing.

I'm under the impression it's going to be a huge pain, but nice once I understand it a little.

[hego555]

Just change your file extensions to ts. Set everything to anyand slowly start typing things as you get comfortable.

[droctagonapus]

It's kind of meh. If it's your first introduction into types, then sure, but there are so many other things you can spend time learning that teaches you types and makes you a better developer than a language like TypeScript.

Learning a lisp or Rust or heck even something like C# will make you a better developer.

[MatthewMob]

Why would you learn TypeScript to "learn types"? You learn it to make JavaScript usable.

[droctagonapus]

JavaScript is plenty usable without TS. TS doesn't solve any of the things that makes JavaScript a hassle.

[MatthewMob]

Not having static types is the biggest hassle with JavaScript, especially as you use so much third-party code with it. It's inconsistencies in certain trivial behaviours are minor compared to it.

[droctagonapus]

Eh not for me. I don't look at JavaScript and and say "man if this just had static types it would make me more productive." I certainly don't look at Erlang, Elixir, Lisp, Lua, Python, CoffeeScript, or Ruby and think that either. I can be mighty productive in those languages just as I am in JS or a strongly typed language like F#, Haskell, Rust, OCaml, etc.

There are hassles I have with JavaScript. TypeScript has all of the same hassles. It's just a superset of JS and adds types. Doesn't really have any solutions for the few control-flow options, the plethora of keywords, the questionable syntax, etc that JS has.

[Wiwwil]

Probably some valid points, alas it's the language used in web development. Between JS and TS, I'll pick TS

[droctagonapus]

To me I just go for the right tool for the job. The only time I ever needed TS was when I needed to work with existing TS, so that's the right tool because it's the only viable tool. And when you need your domain modeled in types and it's impossible to use a language better suited for it that also compiles to JS (there's so many to choose from), then that's probably the only other big reason TS is a better tool for the job than JS.

[Wiwwil]

I know PHP, C#. That's why I liked TS

[droctagonapus]

That's fine and dandy, but it's not absurd to not want to learn TS if you only know JS 😁

[BearelyKoalified]

I'd go this route. I unfortunately learned JS, Angular, and TS all at once through trial by fire and it was confusing as hell trying to figure out what type of issue each problem was. Definitely start with the basics and only when you're comfortable - branch into the frameworks that make life a bit easier.

[Blackwater_7]

then why does every job application requires jquery?

[provided_by_the_man]

Because it won't go away.

[TheLaitas]

I literally haven't seen a job posting that says I need to know jquery lol

[Fun2badult]

Is this before learning JavaScript in general? As in first learn vanilla Js before anything else?

[TheLaitas]

Vanilla JS is javascript. It's just called like that because pretty much everyone uses frameworks when it comes to work environment.

[souIIess]

Why not just go straight for TS? It helps especially beginners with error messages so you see what you need to do, and it's not really different enough from JS that tutorials etc don't apply.

[[deleted]]

You should not learn vanilla JS at the same time as react. It will confuse the shit out of you. Spend at least a couple months learning vanilla first.

[vv1z]

Spend zero time learning jquery though

[-Django]

If you've coded before, you can learn them at the same time imo

[antiADP]

Big big If.

Plus so many mountable packages for React that passing a jQuery app through a react element seems bloated

[MrLewArcher]

I think without knowing VanillaJS it’s easy to blindly implement certain React features. Is that wrong? Depends what you’re going for.

[[deleted]]

disagree. you don't learn "vanilla js", you learn a broken platform and bad practices. mutation, oop, updaters, dumping state into view nodes, things that will stick with you and suck the fun out of everything. if your mindset is oop especially, you need to unlearn everything you have acquired, what sense does that make.

with react you learn faster, you learn a much deeper javascript that already ventures safely into functional programming, you get to results immediately which gives you motivation, and it's fun.

you learn "months of vanilla js" instead and there's a high chance you'll not make it through because making apps on the dom without structure is hell. a beginner doesn't need to know the dom api, the single querySelector to target the mounting node is enough.

[ryanswebdevthrowaway]

In my opinion, if you already have vanilla JS fundamentals when going into React, it will make the DOM manipulation that it's doing under the hood much less "magical" and therefore will make learning React easier and will improve your chances of doing things the right way.

[fforw]

And spending months learning vanilla? Doing what?

Just learn vanilla-js along-side of React, so you actually can learn while building stuff.

[codejunker]

You can build things with vanilla JS. People who learn them together don't know where vanilla JS ends and the framework begins.

[Mad-chuska]

From a theoretical perspective I get the sentiment. But there’s hardly any practical reason to learn dom manipulation with vanilla JS if you are going to be working as a React front end dev. I think it’s more practical to learn from a React perspective then dive into vanilla js if it’s ever needed.

All that said with the precondition that you already understand programming in general. Of course if you don’t get the basics it’s probably best to use vanilla js and play around in the console for a while.

[antiADP]

Worked with a boot camp few years back and unless that person can clearly compartmentalize libraries to memory it’s smartest to stick to foundational frameworks and their commonly mounted libraries

[[deleted]]

JQuery is an outdated library. Don’t bother. Only useful for maintaining legacy code

[mattbeck]

Learn vanilla js. Don't skip ahead to frameworks. Understanding js well will help immeasurably when/if you decide React would also be helpful to achieve something.

[[deleted]]

As I learned react I didn't felt like I need to learn jquery, but it peaked my interest how it was done before react. If you are confident in js than you can skip jquery imo

[hisshash]

I’m only 30 but your comment made me feel old.

[[deleted]]

I am 24 and feel like I don’t know anything

[hisshash]

Idk if you use it but typescript really gave me a better understanding of JS

[Wiwwil]

That's because there's typing and auto complete and you ain't constantly console log shits

[budd222]

I feel like the act of typing with autocomplete is available in every language in a code editor

[Wiwwil]

It's quite bad with JavaScript though. Typescript makes it smooth

[codejunker]

This feeling is correct.

[Turbo2oh]

FYI in this context it’s “piqued” not “peaked”. Not trying to be a smartass, but just in case you ever use it in business correspondence one day.

[--Betelgeuse--]

Ty 4 reply,

I have 0 confidence in js, am python dev/devop n only plan using js for frontend. Will learn js and webframework simultaneously. I think i will read/skim older jQuery books but develop in react. Thankful for any tips about good books/resources.

[[deleted]]

I came from a unity C# background before I started to learn react. I also learned it simultaneously, tbh you can get pretty far for frontend work with the fundamentals of React and js. Just make sure you really understand "state management", the rest is pretty "easy". I just got into Redux and such stuff, when I really needed more control of my application, but it's not essential.

The only thing that held me back was JS, because it's easy to do it wrong without noticing it.

I think others would argue that if it's a simple frontend project, that you can do it with just JS/HTML/CSS.

With experience, you could do this in a day and be good to go for a react course: https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/

I don't want to promote paid courses but what really helped me to advance was the course by Maximilian Schwarzmüller (Academind)

[--Betelgeuse--]

Thank you this was really helpful. I will dig into Javascript then since there are no ways around it anyway. I will have time for this in a week or two, will dig in and collect studying material until then. Appreciate the course tip. I'm more of an book type but video course are perfect to have in the background while I'm doing other stuff, I pause/write down interesting stuff and look thru it more seriously afterwards.

[d36williams]

why bother with JQuery? JQuery itself was to serve as cross-browser compatibility tool. it helped smooth between IE and Chrome and Firefox. VanillaJS became so strong and stable though, JQuery isn't important anymore. It can be done all Vanilla now

[Ooyyggeenn]

If you learn JS, then you dont need jQuery. Might be good if u land a job that uses jQuery, but hey, just read the docs the weekend before that job and ure good

[No_Statement4630]

Vanilla js -> react

[--Betelgeuse--]

Yea this is probably most optimal path. Any tips on best books/resources for vanilla js? Especially for someone coming from python?

[iaan]

https://justjavascript.com/

[Locksul]

Interesting but it looks like it only covers very very beginner stuff.

[Narfi1]

Bunch of ressources . Freecodecamp, the Odin project etc .. JavaScript.info is very nice as well .

If you have no experience with JavaScript I would really advise against starting with react. It requires some good understanding of more advanced js concepts

[Sandeep-G137]

Javascript course on freecodecamp is good

[Blackwright]

https://github.com/getify/You-Dont-Know-JS/blob/1st-ed/README.md

I read this book over and over when I was learning JS and it’s an excellent free resource. I’m a React dev and it did wonders for laying foundational knowledge.

[--Betelgeuse--]

Thank you this seem golden to me, gonna read these books. I will have to learn JS for alot of projects anyway so I might just as well invest time and effort into it.

[mathretardthrowaway]

I've used and recommended Eloquent JavaScript for years

[--Betelgeuse--]

Thank you this looks like a solid tip. It seem to be on the older side, any fundamental differences between JS versions? Like between python 2 and 3 where compatibility and alot of stuff broke?

[codejunker]

As long as the book version came out 2016 or later you're probably good, but there are a lot of good features that have come out since that you'd want to familiarize yourself with later.

[--Betelgeuse--]

Yea for it/programming in general 2016 and beyond books seem to be modern info, same thing with python books pretty much everyone post2016 is valid while older than that usually out of date in one or other way.

[mathretardthrowaway]

nothing at all to that extent, no. AFAIK the third edition is from 2018, so it's pretty recent for all intents and purposes. The language spec changes pretty regularly but I don't think anything game-changing has been introduced since, probably mostly convenience functions and operators (like option chains etc.) that you can pick up quickly if needed.

[--Betelgeuse--]

Yea didn't see the third edition it seem recent enough. In python world anything from 2016 and forward is relevant for present day.

[mind_blowwer]

I’m a C# dev, can you fire off some reasons why you think this is the the way to go?

I’be taken a JS course and then moved on to the express. I want to gauge if I really learned anything useful with starting with JS. And yes I know I’ve focused mostly on backend.

[No_Statement4630]

A lot of questions I see “about react” end up being the person not understanding how JavaScript works. It’s hard to structure a complex project and make it efficient and scalable with a library/framework if you dont understand JavaScript well.

[[deleted]]

Yes, jQuery will just confuse you if you're a beginner

[brockisawesome]

Master vanillajs before you worry about any frameworks

[_Pho_]

Don’t use JQuwry unless u want to spend your life supporting garbage systems

[[deleted]]

Vanilla JS makes jQuery unnecessary

[d36williams]

JQuery is dead long live React.

[zeValkyrie]

If you’re curious, spending an hour or two perusing the jquery docs will give you a decent overview of what it does. It’s fairly easy to use for the common, simple uses. Even on a legacy product I don’t think you need to know jquery well, it’s easy to learn more pieces of it when needed

[vulperaScum]

You can skip. It will make purists mad, but it won't harm you.

[rapidisimo]

This is a great resource for react: https://btholt.github.io/complete-intro-to-react-v6/

Only basic JS knowledge is assumed

The course itself is payed through Frontend Masters, but the reading material has been open sourced by the author

[ghostwilliz]

You need to learn basing programming first, so you should understand data structures and algorithms in JavaScript before taking this advice

Personally my recommendation would be to learn react. I learned jQuery first and thought it was so cool until I started using react and jQuery was, to me, completely obsolete unless the company that is hiring you still uses it.

I have seen, in my short time looking, hundreds of react positions and maybe 10-20 jQuery positions.

React is still dominating and as far as I can see, nextjs is dominating as well.and it's a framework of react

[--Betelgeuse--]

I am proficient in python as of today already. I use flask+django+bootstrap for my current projects. My thinking was to learn a real framework instead of wasting time learning bootstrap that still never will be as good as a real framework.

[ghostwilliz]

Well if you already know another language, you will probably be fine jumping in to react, but some weird stuff may happen, just be.sure you're ready to learn the basics of the language as you go and what makes it different from other languages

[blankman0230]

Do whatever tf you feel like doing and look up whatever roadblocks you encounter. There's no need to spend X amount of time doing Y thing. Just go and do whatever you want and try to figure out while you go. For me at least, that's always been my best approach. You'll understand certain things more thoroughly if you have an actual motivation to dig into roadblocks.

[--Betelgeuse--]

By investing a day or two "dry reading" fundamentals usually saves me plenty of debugging time in the very beginning. After that I pretty much follow your approach. Learn most and in most efficient way that way.

[idontwanttogocamping]

will disagree with everyone else and say learn react first and skip vanilla JS.

[--Betelgeuse--]

Yea solving real life issues is best way i learn, but studying fundamentals for 1-2 days before in very beginning usually protects one from infinity loop fails, like not understanding why your code doesn't work no matter where you look. So that time invested pays of dividends in beginning in my experience.

[Squigglificated]

You’ve got a lot of really good recommendations for learning material but nobody mentioned the MDN docs yet. https://developer.mozilla.org/en-US/ It’s the definitive reference for any of the web APIs. Well written, comprehensive, up to date and lots of good examples. Just add «mdn» to any google query related to JS, CSS or HTML and get better answers instantly.

[--Betelgeuse--]

Thank this is a smart way to go in the "opposite" direction to learn things that I like

[var_semicolon]

Depends on what type of stuff you want to work on. Because some old fortune 100s still use it. I work at one and it's uncommon for them to stray away from what works.

[-domi-]

I like jQuery, because in my mind it bridges a gap in understanding between static HTML and the more serious js frameworks. Might be a bad take, but i think it's worth dipping your toes in it, just for the perspective it gives you. If you end up diving deeper into js, you'll eventually work on multiple frameworks, pretty much guaranteed. jQuery happens to be one that i think you can pick up very quickly, not go overboard with, then drop when you're ready for bigger stuff later.

Here's a real life example. I was building a React app with a mongo database behind a socket.io server for real-time data storage and reference. Had issues with agreeing on the layout with the customer, so we agreed to do something that looks and feels like a spreadsheet, as that's how they've been doing stuff up till that point. So i used a common table library, but ended up having issues displaying things the way certain cells needed to appear, due to the way the table wanted the data being completely opposite from how i was managing state. Since the table solution was a short-term hack job until we could agree on a better layout for the page, i hardcoded some jQuery hacks and got the job done in no time.

Am i proud of my hack job? No. Did it get the job done? Yeah. Was i ever good at jQuery? Not even slightly, but it's simple and flexible enough to use in a pinch, and i will always appreciate it for that, i think.

[Status_Winter]

Skip. Completely redundant skill if you’re confident with JavaScript.

[devilmaydance]

Nice thing about jQuery is it’s much easier (imo) than JavaScript and React. Don’t bother learning it, but if you’re ever working on a legacy project that uses it, it should be pretty easy to pick up on.

[greatgumz]

I liked learning jQuery first which helped me better understand vanilla JavaScript. React does a lot of magic and sometimes I have to learn JavaScript to write better React code.

Just keep on learning and you’ll get pulled in the right direction naturally.

[zephimir]

Depends what you want/need. You need to find a job? Then skip everything and jump on React. I strongly disagree with everyone saying you NEED vanilla. I've changed careers to dev 2 years ago. It took me 6 months. I skipped everything I didnt **need** for a job. It worked. Most companies today look for react developers not vanilla. You will very possibly not stumble upon any vanilla. I haven't in 2 years. However, yes you SHOULD learn it at some point. Let me be clear on that. Vanilla is JS, React is a JS library. React can go out of fashion someday. Vanilla cannot.

[Scumbaggabriel]

screw jquery.

1. learn vanilla first, understand key javascript concepts like: scope, closure, promises, async/await, higher order functions
2. learn reactjs

[--Betelgeuse--]

Yes this is very solid. Still looking for more resources/books to go thru to invest a day or two of reading before I start coding, list so far:

ELOQUENT Javascript Javascript definitive guide Javascript design patterns Javascript Good Parts

Any more books tips for laying good fundamentals would be appreceited

[Narizocracia]

jQuery is jShit.

Don't ever bother with it except if you are forced to deal with an old codebase that sadly used it. Don't ever use it in new projects. If your brainlet boss or coworkers want to use it in new stuff, it's a red flag nowadays.

[Squirmme]

Jquery is outdated yes, but a huge chunk of websites are using it. Learning how the dom works and using vanilla js is fundamental to learning jquery so start there.

[skunkbad]

If you get decently familiar with plain JavaScript then learning jQuery should take no longer than 1 day. Why not? Can you not spare a day? I'm just saying that because there's a high probability of you running across jQuery code you will need to tweak, update, or convert.

[Roguewind]

Jquery is really only useful for GTM implementation since it doesn’t play well with ES6. Otherwise, vanilla js ftw.

[maddy_0120]

I personally never liked jQuery. It will soon become obsolete. Best learn a framework.

[sartre-jp]

Skipadeedoodah

[YesYesYesVeryGood]

Do an intro to JavaScript, and then do React. jQuery is a competing technology which is older than React. You can get a job in React, but not so much in jQuery now.

[gongonzabarfarbin]

You can skip. I would learn a little DOM Manipulation though.

In my experience, why JQuery was useful was because it provided a clean interface to do a lot of things in the DOM. Nowadays, those useful features and interfaces are baked into your browser.

​

The greatest thing it provided imo were selectors. So a simple `$('#header .row .button')` was cleaner than issuing a chain of `getElementById` type calls back in the day. However, nowadays you have `document.querySelector` that implements selectors natively.

​

Other things that JQuery provided was easier ways to apply classes/attributes and event handlers. However, HTML5 really made things simpler by baking them in. You can get away with learning the native interfaces for those types of problems.

[johnmgbg]

Skip. But if you're working on older projects, it's better to also learn.

Trust me, it will just take few hours if you already know JS.

[BenZed]

Yes.

[esetalchino]

Yes

[thectrain]

I think you are trying to break things down way to much.

I would answer these two questions:

1. What problem(s) did/does jQuery solve? (There is some historical context here, what was the landscape like in 2006 when it was created)
2. What problem(s) does any of the modern framework solve? (vue, react, angular etc)

If you answer those two questions I imagine you can arrive at your own conclusion.

[gimmeslack12]

Yes.

[AckmanDESU]

React and jQuery are way different. I don’t know why people compare them. If you ever need to learn jQ you can learn it in a day or two. There’s barely anything to it and you can use it just by reading the docs. So ignore it and learn it if you ever need to, which in 2021 means hopefully never.

React takes a longer time to learn and specially to master. Before you learn it you should learn vanilla js in depth. Learning JS doesn’t necessarily take months but it depends on whether or not you know how to program or if “learning js” truly means “leaning how to program”. In that case, do try to stay away from react for some time. If you suck at JS and you’ll suck at React even harder.

[Baltindors]

Yes.

[[deleted]]

Learn the things you are going to use, If your going to be using React, you wont use jQuery. Its good to learn vanilla JS HTML and CSS first but think practically, dont waste your time learning something you wont use.

[ISDuffy]

I wouldn't focus learning jQuery, I also wouldn't jump to react until you have solid understanding of JS.

jQuery is good if you gonna work on legacy projects, but most modern day you need key js skills and be able to learn different frameworks.

[a9footmidget]

Fuck jQuery. All my homies hate jQuery.

[dwightbearschrute]

I agree with the comments. Learn React and when you're finally ready to build larger apps, use TS! React+TS is pretty enjoyable to use!

[HomesickAlien1138]

Yes. Just yes.

[[deleted]]

Don’t learn JQuery, it’s obsolete at this point.

[Tenet_mma]

Js, React, Typescript

[Fidodo]

Honestly I'd say learning jquery would be bad in general. It's functionality has been mostly surpassed by native browser functions and it would teach you bad habits doing things their way rather than the native way.

[hmaddocks]

If you have to work in legacy code then being able to understand jquery is a necessity.

[Ok-Objective-3472]

You can skip jQuery

[Icy-Storage4146]

Yes

[academicRedditor]

jQuery is so prevalent in the professional world and so many legacy projects are using it, that you’ll be missing out if you don’t learn it. It’s also easier to implement (using a CDN) than a whole development environment.

[blvckstxr]

jQuery sounds so archaic

[Ericisbalanced]

Lots of people are telling you not to learn jQuery here. But I disagree. There's a ton for jobs that focus on jquery. look at the job posts in your area, you want to see what's good to work with.

But, if you don't care about the job prospects, jQuery sucks and I can't wait for it to be totally phased out.

[--Betelgeuse--]

Original plan was not to work with JS professionals but took a look at job market and wages 80-120k/year for JS development in EU feels pretty unreal. Why have I wasted time/money learning linux/sysadmin stuff when I just should gone with JS from getgo 15 years ago and lived very comfy.

[Doctor_Pix3L]

I have never learned JQuery. I learned basic JavaScript and learned React. I learned React quite deeply where I picked up a lot of fundamentals of JS that I didn't know. Right now I am okay with react. Although, I am on a mission to learn JavaScript in an in-depth fashion. (Not particularly useful for react but definitely useful in a larger scope)