3 ms·
The problem is not frameworks; the problem is object oriented programming. Simply put, OOP lends itself to kitchen-sink frameworks because it is the only way t
by MatthewPhillips 14y ago
The problem is not frameworks; the problem is object oriented programming. Simply put, OOP lends itself to kitchen-sink frameworks because it is the only way to really share code in OOP. We write these large hierarchy of objects and then, because we have to carefully maintain state, we mark most of it as private, or sealed. Then we give precise instructions on how to consume and use the code, and even more precise instructions on how to extend it.
- UK-AL 14y agoWell that's strange because Django didn't use much OO either when I used it in the past, only for the ORM.
- anthonyb 14y agoAlso this is Python, so you can poke the internals however you like :)
- sashahart 14y agoYou can, but that doesn't mean you should. It's brittle. If your app or library breaks because a minor update to a dependency changed those internals completely, you can't say you weren't warned.
- bad_user 14y agoYou must have been using a different framework called "Django" than I did.
- jonknee 14y agoHave you used Django much? Some classes you run into frequently (besides Model): * Form * HttpResponse * All middleware * Template * Etc, it's all classes except if you write function based views