Using too much of a framework's special sauce increases the dependency - not good!
But what makes a framework worth using is its "special sauce". That's what makes building rhings easier or faster or safer. If your goal is to avoid using the tools that the framework provides ... Then why use the framework at all?
I use Vue for application structure and managing the render cycle when state changes. Those are the two primary benefits Vue offers. Yes, like other frameworks, Vue can do more than that, but I don’t just go all in because I’m using a given framework. I like to keep things flat and vanilla when there isn’t a compelling reason not to. And I like the freedom to use other libraries that are better than what the framework offers (things like dates, i18n, UI library)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
But what makes a framework worth using is its "special sauce". That's what makes building rhings easier or faster or safer. If your goal is to avoid using the tools that the framework provides ... Then why use the framework at all?
True, but didn’t I say “too much special sauce”?
I use Vue for application structure and managing the render cycle when state changes. Those are the two primary benefits Vue offers. Yes, like other frameworks, Vue can do more than that, but I don’t just go all in because I’m using a given framework. I like to keep things flat and vanilla when there isn’t a compelling reason not to. And I like the freedom to use other libraries that are better than what the framework offers (things like dates, i18n, UI library)