"Frameworks are overhead. You need to learn them. They can be in the way. They may have performance implications.
Why not just avoid them altogether? Use the platform, whether that may be the web browser or the operating system or whatever else.
I think this is an illusion. A platform is already a framework. If it fits what you want to do, great. But it may just not be a great framework for your particular purpose."
@faassen I know jQuery, I know VueJS, but I've never learned Javascript and have no interest in doing so.
The fact that everyone is constantly scrambling to get away from the browser APIs, either from HTML to their preferred frameworks or from JS to TS or CSS to Tailwind or even webapps to mobile apps should tell the browser Devs something about the current state of affairs.
@divclassbutton @faassen I have been going the other direction in my career - closer and closer to the native web APIs in while also _looking at_ and _learning from_ the abstractions that frameworks offer.
If I need something on top of the API I’ll prefer libraries as I’ve been burnt by frameworks too often (angular 1, react, prototype, jQuery, dojo, …).