|
|
|
|
|
by jbbarth
3684 days ago
|
|
This argument often comes up and I'm genuinely curious why people think Django is less "magic" than Rails, in my experience it has been the opposite. My experience with Django (for instance: class-based views and admin parts) is actually that you have dozens of magical classes or methods and if you don't know them all, you're screwed. Often when I try to do something, many aswers on StackOverflow boil down to "just override a_method_that_is_hidden_somewhere()" or "just use ListButWithSpecificBehaviorView(), easy you see?". Are there any specific example you have in mind where Rails do something magical that requires more code in Django but where Django is more explicit? PS: not trying to start a flamewar, both are OK-frameworks, bla bla bla ;-) |
|