On another note here a a few claims framework authors make which are usually short sighted 1. Frameworks promote code reuse Frameworks however don't promote r

On another note here a a few claims framework authors make which are usually short sighted 1. Frameworks promote code reuse Frameworks however don't promote reuse within different versions of the same framework, which makes the code reuse claim hypocritical at best. Where is the code reuse between Angular 1 and Angular 2 ? Libraries also promote code reuse by the use of shared object files (C) or modules (Python, Node.js ...) and it is usually more long lasting. 2. Frameworks are easier for beginners to use Frameworks get difficult quickly once the initial use case is run out. Frameworks appear deceptively simple because they hide complex code under the rug, but anytime you need to do functionality similar but different to that initial complex code, you will have a problem. With a library, you can inspect the code ... copy it and edit it to do what you want, it is not as simple with frameworks especially when you have to deal with 100 levels of inheritance. In a way frameworks encourage code illiteracy. 3. Frameworks are not composable Using two or more frameworks is next to impossible because of all the assumptions frameworks make. Frameworks are totalitarian in this regard. 4. Object Relational mismatch is real By forcing the object model on everything, it makes understanding non OO models for data, which is most data ... very difficult. Relational model is more generic as it supports references and is obviously more efficient.