To me it's not something you should learn in the first place apart from just enough to turn the garbage people make with it into something useful and lighter weight. It sure as shine-ola has no business EVER being used on websites due to it's bloat, ineptitude, and ACTIVE promotion of bad methodology... like using the equivalent to querySelectorAll every bloody time you access ANY element, daisy-chaining method calls for massive memory bloat, and slopping content into pages innerHTML style instead of using the DOM.
That last one being part of what makes me wonder just what the **** people are flapping their gums about when they talk about jQuery as being a tool for working with the DOM, as to be brutally frank it side-steps learning how to use the DOM, how to walk it, how to leverage it for lower overhead, or to build directly upon it!!!
ANYONE calling it a "DOM Manipulation" tool doesn't know enough about HTML, CSS, JavaScript, or the huffing DOM to be talking about it! -- no offense, but someone's been blowing smoke up your backside.
But then, the folks who advocate the use of jQuery have generally been pumped so full of smoke rectally, I could chop them into small bits, put those bits in a styrofoam tray, and win a BBQ competition. Hmm. That would make great lyrics for a Cannibal Corpse song...
As I've said hundreds (thousands?!?) of times, EVERYTHING I've ever seen done with jQuery falls into at least ONE of these categories:
1) Stuff that would be less code without the framework -- NOT counting the size of the framework against that total.
2) Stuff that's either HTML or CSS' job.
3) Stuff that has ZERO DAMNED BUSINESS ON A WEBSITE IN THE FIRST PLACE!!!
It is a tool for the nubes, rubes, and fools easily duped by "ooh shiny" and echo-chamber lies, all because they don't know enough about the underlying languages to even be building websites in the first place -- at least not if you care in the slightest about separation of concerns, progressive enhancement, graceful degradation, or JOE FORBID accessibility!