This got a lot better in 1.4: TemplateResponse and the list filter API meant some gnarly code removal on my biggest customized admin project.
That said, I also chose to implement many of my admin changes at a higher level: templates which use jQuery, etc. and interact with the REST API for e.g. complex object creation are much easier than the crazy form / widget hacks I used to try.
Re:Why Django Sucks
by mattdeboard on Thursday June 07, 2012 @07:09AM
(#4078378)
Yeah agreed, I just started writing js apps with backbone and dropping them into wherever in the amdin
I'm about +10 on that approach: customize the admin until you hit a difficult point, then stop trying to hammer screws.
Re:Why Django Sucks
by mattdeboard on Thursday June 07, 2012 @04:10PM
(#4081086)
But the only tool I HAVE is a hammer!
I have no problem with criticism of Django, but to write a presentation called "Why Django Sucks" is bombastic, misguided link bait - replete with rage comics and whatnot.
It's just not constructive for the discussion, interesting as it may be.
'replete' with a few Reddit-style comics, of which exactly one could be argued is a Rage comic (though it actually isn't).
Re:Why Django Sucks
by zeemonkee2 on Thursday June 07, 2012 @10:17AM
(#4079114)
It's a long-standing tradition for DjangoCon to have a "Why Django Sucks" presentation. And a healthy one IMHO.
But it can be very difficult to do relatively simple things with Django sometimes, mostly in the admin pages. Admittedly, this is a pain point people bring on themselves by trying to do too much there, but it's a big red swollen example of how too much interleaving and complexity make it painful or impossible to reason about what's happening.