I used to hate frameworks when I first learned javascript many years ago, and I refused to use jquery, backbone, ember and whatever else existed. but then for some reason I found myself creating a kind of framework for my own use inside my small personal projects all the time. basically I would develop abstractions for handling and updating state, but my pseudo-frameworks always failed miserably because I couldn't get my updated state to be reflected into UI in an abstracted manner, I tried.
Discussion
then I read a post about react which had just been launched (and which I initially despised) and I thought it had found a way to solve exactly what I had been trying to solve, then I liked it very much, and it took a while after that moment for the rest of the javascript people to start liking it too, but eventually that happened, and it spun the creation of dozens of other microframeworks all based on the same principle, which I think was quite ingenuous.
that isn't to say I love react today. It is probably very bloated -- but I have tried many other frameworks and it turns out react still feels simpler and better than them all. except for this one: https://dev.to/raquo/my-four-year-quest-for-perfect-scala-js-ui-development-b9a
oh, right. every time I have to start a new javascript thing I still try to make it without frameworks, but I rapidly realize I have to use some framework to prevent me from doing manual tasks (maybe I took the DRY principle too seriously). the last one was https://github.com/nbd-wtf/satdress