A question came up in a semi-recent ShopTalk episode about the use of jQuery in tutorials.
Ah helpful, but there is really no need for jQuery here: Swapping Out Text, Five Different Ways – http://t.co/5gyFGmoCVp
— Smashing Magazine (@smashingmag) July 3, 2013
So here’s how I feel about it.
This blog is a reflection of things that I learn. I use jQuery a bunch. So when I translate things into a tutorial, I do it how I would do it.
The goal of a tutorial is to teach an idea and do it fairly succinctly.
Let’s say you wanted to select a button with a certain class name and change some text when it is clicked. To avoid any dependancies, maybe you do
document.querySelectorAll(".my-button"). But that will return an array so you need to use  at the end of it to target the element and attach the event. Or should we just use
querySelector instead which selects the first? Or should we run a loop or map over the array to bind to all of them? Or should we have used
getElementByClassName? What about browser support? Should we talk about polyfills for that? Or should we just add an ID and use
getElementById since that’s likely a best practice?
Or, we could just do
$(".my-button") and get on with the tutorial. All of that stuff is interesting and worthy of discussion, but not in every single tutorial every single time. jQuery allows the concepts in tutorials to shine without getting bogged down in detail.
Right now I feel like jQuery is still a pretty important part of the front end stack, well worth learning, and still appropriate to use in tutorials.