ember.vs.backbone.md

EMBERJS	BACKBONEJS
-built in support for standard features yields a larger package size	+smaller package size
+supporting many common features means library's dependencies list will grow less over time	-achieves smaller package size by sacrificing built in features
-if the common features aren't needed then they are unnecessarily included	-smaller package size advantage is lost if many libraries are used to compensate/extend backbone's feature set
+hailed as strong when for multipage, navigational, long-term project	+hailed as strong when project is a single page or part of a page (widget)
+has a default testing stack using QUnit	-no default testing library, implies a task for choosing and implementing a testing stack
+More opinionated can be good when multiple teams or developers are working in the same project	-Less opinionated can be bad when multiple teams or developers are working in the same project. Can lead to inconsistencies