For a moment I thought VanillaJS meant plain JS... Ugh I'm too old for this s.
VanillaJS is plain JS ;-).
It is confusing though. In a way, all JS besides compile-to languages (like Typescript) are "plain JS" in that they don't do anything outside of the standard JS syntax. Vanilla really refers to how you call the browser APIs. It would make sense that VanillaJS would be coding for the browser with no additional libraries, but http://vanilla-js.com/ begs to differ. I think it's because browser APIs are so inconsistent between vendors (Chrome to Safari to FF to IE) that you'd have to be insane not to use some sort of "normalizing" library. Sort of like how a reset.css or normalize.css is always used. In any case, it's more complex/confusing than you'd hope.
edit: nothing to see here, just someone who fell for the VanillaJS site :P
You know vanilla-js is a joke right?
Oh my... No, I had no idea. That 100% tricked me. Well done.
Well in that case, today is a little brighter.
I'm interested to see where this goes. As a very long time jQuery user, seeing the benefits of this as a beginner would be far outweighed by the huge amount of literature and history of jQuery.
The size of jQuery is definitely the negative point here, and I think for Bliss to be super-successful, they will need to market it around that idea first and foremost. Some very successful and seasoned developers don't know (or frankly care) about "prototype pollution" - they primarily care about speed of development, maintainability, and performance.
Let's hope it gets the right attention on major projects.