What are the pros and cons of using backbone?

Question

JavaScript

Where is the line when you should use backbone and what are its pros and cons?

Answer 1

Backbone should be used when you can extract a model from your data and make a collection of models. But to write good code with Backbone, you need skill (it has a rather high entry threshold).

Answer 2

It seems to me that if your backend consists of a REST API, in which there are more than three methods, you can start using it.
Cons - it's not a framework, it's a library. Bb won't help you figure out how to organize your code.
Pros - the library is quite powerful and convenient, and easily extensible.

Answer 3

I've been writing on Backbone for a long time. Therefore, from experience I will say:
1) Those who love underscore will most likely love Backbone
2) Backbone is quite lightweight. On the one hand, this is good, on the other hand, you have to get the missing functionality with third-party plugins, or write it yourself. Third-party plugins and self-written code are not always as good as Backbone itself.
3) Backbone needs jQuery (or its replacement). This in itself is not a problem, but it should be kept in mind nonetheless.
4) Backbone is more of a library, that is, you can take parts from it and use it completely separately
I'm looking forward to using Backbone in large and medium projects, as long as there are qualified developers who can write a competent architecture with it. That is, someone must control so that the project does not turn into a mess.