It's ok to not be up-to-date with every technology choice. No matter how smart you are, please realize that front end engineering evolves at a dizzying rate, with new hyped up libraries, frameworks, techniques, and best practices emerging all of the time. Even if you do front end stuff full time you'll go mad trying to use half of what you read about.
I think that the best way to learn this stuff is to pick a problem that you want to solve and learn the pieces necessary to solve it in a logical fashion. You'll start out with HTML, try and style it with some CSS, and then add a touch of interactivity with some JQuery. Then you'll start to have more and more code and you'll logically reach out for tools like Sass, and RequireJS and others to organize things when it becomes overwhelming. Then once you start solving bigger and bigger problems you'll eventually look into Backbone, and maybe other frameworks once you can't build a maintainable solution with what you know. Learn stuff as appropriate to solve the problem you're working on.
Before jQuery going mainstream there was Spry, and then it faded away.
If jQuery ever goes away, the good ol' JavaScript will still be there for us.
Find a problem no matter how trivial it is, turn that problem into a solution in the form of software. Use the tools that would be best for the project. It doesn't matter how recent the tool is, how many people use it, how cool it is. What matters is that it gets the job done.
I've finally settled on an idea and buckled down and got to work.
jQuery really does smooth out a lot of the cross-browser incompatibilities, but it doesn't excuse you from knowing javascript. Javascript: the good parts is old, but still a good place to start.
To cement your JS skills, do the project in node.js. I think that really helped cement how I think about JS, and it's not too far out of the way for a backend developer to understand, callbacks aside. (Using a noSql store will help in this environment, as there's no great SQL ORM solution right now and your purpose isn't to get bogged down there.)
As mentioned, Mozilla Developer Network is one of the best documentation sites.
From there, you can turn your jQuery site to a backbone or ember or angular solution to see how that differs. Don't bother with all of them. :) If you can do all that, you're going to be in pretty good shape.