Re:Why Django Sucks, and How we Can Fix it [slides]
by orangesunshine on Wednesday September 08, 2010 @08:58PM
(#1674060)
There already is a fork (django-experimental), though interest seems to be limited at the moment.
There has been limited work on it. Essentially I just fixed the demented logging system... though I will probably fix the demented templating system, and ORM in due time.
Re:Why Django Sucks, and How we Can Fix it [slides]
by jnoller on Thursday September 09, 2010 @12:43PM
(#1675952)
Isn't the logging system being fixed in 1.3?
Re:Why Django Sucks, and How we Can Fix it [slides]
by jnoller on Wednesday September 08, 2010 @08:00PM
(#1673940)
Not all ideas are good ideas. Just like python-ideas threads that crop up, not everything belongs in the framework, and some things are better off elsewhere.
Re:Why Django Sucks, and How we Can Fix it [slides]
by alttab on Wednesday September 08, 2010 @09:10PM
(#1674079)
Where though? Django lacks and clearly defined interface for framework plug-ins, python eggs don't exactly ooze with win here...
Re:Why Django Sucks, and How we Can Fix it [slides]
by jnoller on Thursday September 09, 2010 @12:39PM
(#1675942)
Just because python packaging sucks doesn't mean Django should drop it's "design integrity" just to throw things in people "really feel the need for". Otherwise Django bloats, gets complex and to big to deal with, and it goes the way of Zope.
It's a pity, django could go a lot faster than it does. I would not be surprised at all to see a mambo / joomla style fork happening to django if the core team does not heed these warnings.