Not using an MVC framework is often fine if you're working alone on a project but you might just end up reinventing angular... Then when new people come in to

Not using an MVC framework is often fine if you're working alone on a project but you might just end up reinventing angular... Then when new people come in to your project, the learning curve for them will be steeper than Angular - Also you won't be able to hire any 'batteries-included' programmers because nobody will know your framework when they join your company. Worse, engineers might refuse to join your company if they see that you've built a custom solution from scratch... Chances are that your framework won't be as good as Angular or React. Maybe you should try Google's Polymer framework? I've tried all the major ones and Polymer is the least 'frameworky' one.