When to use JS frameworks

Question

JavaScript

Hello, I wanted to tinker with Angular, but I couldn’t come up with a task for myself, and I thought about when it’s really worth using JS frameworks?

Answer 1

The Angular manual ( docs.angularjs.org/guide/overview ) has the answer:
When to use it:
> Angular was built for the CRUD application in mind.
When not to use:
> Games, and GUI editors are examples of very intensive and tricky DOM manipulation. These kinds of apps are different from CRUD apps, and as a result are not a good fit for Angular. In these cases using something closer to bare metal such as jQuery may be a better fit.
In general, Angular is good for Ajax applications with client-side templates, forms, and tables.

Answer 2

Specifically, AngularJS saves a lot of development time. On one project I met the same logic implemented in JSP + jQuery and in AngularJS, it just happened. So, the implementation in AngularJS contained about 10 (!) times fewer lines of code. This is because AngularJS follows the right ideology: a declarative description of the user interface.
Of course, in comparison with other technologies, AngularJS may not look so advantageous. However, he does his job, and he does it well. Please note that in addition to the dynamic interface, AngularJS, and other JS frameworks, save server resources. Or they can completely eliminate the need for server logic.
Herean example of a Firefox extension written in AngularJS (by me) that pulls data from oDesk, expanding search capabilities, and does not require additional server-side logic.

Answer 3

AngularJS is worth using when the answer to the question "will this project exist for more than a week" is positive.
When jQuery was more familiar to me and the necessary site looked “simple” initially, I started on jQuery, then, as usual, I needed to add this little thing and here a little bit ... If I started right away with AngularJS, there would be many fewer lines of code and glitches too. AngularJS gets rid of a lot of routine, boilerplate code.
Then I generally realized the big difference between declarative and imperative style, and now I very rarely include jQuery.

Answer 4

When the costs of using the framework during beta development are more than offset by the savings that will be achieved with the further development of the project and support.
The issue of using frameworks is a matter of balance.
The second question is which framework you need to use for your specific task, it completely depends on the task and the purpose of the frameworks :)

Answer 5

When its use will significantly simplify the code and speed up development.