If your application is nothing more than a good old-school example of the Calculator application — you should switch from VanillaJS to any of the offered frameworks.
Well, unless your page is even a bit more complicated than a simple calculator — we’d say “all the time”. Here’s why:
- All popular frameworks follow the best industry standards and promote healthy engineering practices
- Competition is a good thing, SlickSpeed tests resulted in a much faster selector engines such as Sizzle. Not having to worry about trivial DOM bugs led to more complex libraries which are created on a daily basis. All of this means that entry-level developers can have access to very powerful plugins.
Choosing a framework should never be about the number of features that a particular framework can provide. It’s clear that the terms like ‘next generation’ can sound very appealing, but what it comes down to is the actual functionality of the framework and how that functionality can be used within your project, app or software that you are building.
Some frameworks provide more experience in a sense where the framework is built by sensational developers with decades of experience behind their backs, whereas smaller web frameworks will focus on community-oriented features that can be incorporated within different framework modules.