Nonononono this is a horrible idea. Vanilla js is the whole reason all these frameworks were created. I guess if you don't care about the 1000+ hacks and workarounds to make your code everywhere you're right.
Might as well call it "vanilla chromescript" if you're going that route. Outright rejecting everything that was built for a good reason is worse than covering up bad skills with a bunch of libraries. At least the libraries actually work
But devs should have a firm understanding of Vanilla JS so that when (not if, but when) they need to do something the framework designer never thought of, they'll be able to develop a workable solution.
In fairness to Wes Bos, he says right on the landing page that "these things are great and often needed, but can obstruct learning and constrain initial understanding."
Keep in mind we're not talking just about JS on the web running in web browsers. It runs on servers. It runs as standalone applications. If you are targeting a non-web environment you're not writing for quirks of different browsers, you know the runtime environment you are targeting explicitly. It isn't that bad.
Might as well call it "vanilla chromescript" if you're going that route. Outright rejecting everything that was built for a good reason is worse than covering up bad skills with a bunch of libraries. At least the libraries actually work