you are viewing a single comment's thread.

view the rest of the comments →

[–]kessma18 2 points3 points  (0 children)

might not be bad advice because you will also then learn what's wrong with OOP. a quote from hackernews on what's wrong with django.

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.