JavaScript framework or library?

Question

JavaScript

The author of this post writes:

In short, we're stuck in spaghetti code. Fortunately, there are modern JS frameworks

Meanwhile, examples on todoMVC using Angular, Dojo and others look much more complicated and incomprehensible than examples on JQuery and Vanilla. Plus, the author of this and this post refers to the rigid organization of the negative features of the framework. So where is the truth?

Answer 1

I propose to the author of an unconventional review of Angular to announce a reprimand for having heard a ringing, but does not know where he is.
I consider a rigid organization more of a plus than a minus. In addition, this is only a rule, and if you really need it, you can step aside.
And I propose to approach the issue traditionally with the requirements of the task. For a small page with a form for sending contact information, it makes no sense to twist the angular, for a large application it makes sense. Since the framework allows you to flexibly build data relationships, track them.
The library, in turn, solves a specific problem, for example, jQuery plugins. No one forbids using the library call directly in the angular code, on which, in fact, the logic of the directives is built, which encapsulates the work with libraries.

Answer 2

Some pretty interesting thoughts on this are here: https://andywalpole.me/#!/blog/142134/2015-the-end...
The framework is VERY good for those who don't know where to start. With the growth of professionalism, you can think about your vision of building architecture.