why Backbone is useful, why it might suck - mmedrano9438/peripheral-brain GitHub Wiki

CONS:

• data model also represents the API
• is a problematic design decision which can cause a lot of confusion for developers
• There is no out of the box support for deeper models
• really easy to make many small updates to the DOM for a single user interaction. For large data structures, this can lead to a poor user experience
• supporting different URI schemes, can sometimes be difficult
• lack of a controller building block
• unit testing is very hard
• creates an empty div element for each Backbone view. This can lead to a lot of redundant DIVs in the generated HTML
• “we want to favor the normalized, relational approach to data modeling on the client side, over the giant single global blob of deeply nested JSON approach” in other words i believe its saying that node js would be better

/////// PROS:

• gives you space for making your own development and architecture decisions
• simple and flexible and requires only a few minutes to get started,
• Documentation is also good and solutions to almost any problem exists
• simple inheritance model