I think the definition of Framework needs to be defined. Everyone seems to think that packaging up a bunch of tools is a framework. I would contest that that

I think the definition of Framework needs to be defined. Everyone seems to think that packaging up a bunch of tools is a framework. I would contest that that is wrong. A framework has certain policies and flows that must be followed to allow the program to work. If you bundle up a set of tools, then you have a toolbox. A framework might have a set of tools, but it also has a methodology behind it. If you don't subscribe to that methodology, then that framework isn't for you. I am saying this, coming from the background of not using frameworks because of the bloat and because most of my applications weren't that large. I have used backbone and several other backend frameworks (python and PHP type) and found that they are restricting. For me, programming, coding, hacking, whatever you want to call it is about the freedom to be able to do whatever you want, how ever you want. Yes, I know there are best practices, and there are certain things you aren't supposed to do, but a framework forces you think in a certain pattern, to follow certain rules. Yes, you may be able to develop faster (if your application fits in the scope of the framework) but you have lost much of the freedom that code gives you. I understand people using frameworks. I sit right next to someone who enjoys them very much. But for others (including myself), they are not the next greatest thing to sliced bread because maybe I don't want my bread sliced, but instead, I want it some other way.