@baldur That must be why I never managed to learn much JavaScript. I don't have the kind of mindset where it would even occur to me to call it "vanilla" rather than "plain". What has food flavouring got to do with it?
@artkavanagh @baldur I learned about JavaScript when it was, well, just JavaScript, and to me all of these new things are “JavaScript frameworks/toolkits” or jQuery/Vue/React, whatever, full-stop, things in their own right (no need to use the word “JavaScript” with them at all).
I understand the author’s point, but names are important, and by giving in to the practice of using “JavaScript” alone to mean “some complete coding system written in JavaScript” without any pushback is saying that those things are the only thing JavaScript is, rather than that so-called “vanilla JavaScript” is JavaScript, a very capable thing in its own right, and those other things are toolkits that build upon JavaScript proper. It’s like kind of like calling UIKit/CocoaTouch “Swift” when Swift is used to write code for all sorts of toolkits, not just Apple’s.
@baldur @artkavanagh I imagine there’s a bit of an age factor involved with perception, too—if you weren’t aware of/familiar with JS prior to the rise of the frameworks, it’s possible your first/only exposure to JS was a framework, which then shifts your whole frame of reference. So I can understand how we got to the current trend, but I still think it’s important to get names right.