Re:Why Django Sucks
by MatthewPhillips on Wednesday June 06, 2012 @10:01PM
(#4077224)
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.
[ Parent
| on HN ]
Well that's strange because Django didn't use much OO either when I used it in the past, only for the ORM.
You must have been using a different framework called "Django" than I did.
Have 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
Also this is Python, so you can poke the internals however you like :)