News for hackers. Stuff that matters.
Re:Why Django Sucks, and How we Can Fix it [slides] by wisty on Thursday September 09, 2010 @05:59AM (#1674910)
Zope seemed to have great people behind it, and was very solidly built, but it seemed a lot more monolithic, which ended up polarizing people.

Django really benefits from the ability to swap out everything. People who hate the default libraries just find something better to use.

No migration? Use South. Some people run Django on Twisted or Tornado. There are different template libraries that people use. I'm not sure if the model layer can be swapped out so easily (without messing around with custom user authorization), but there's nothing to stop people using django models for authorization, and a separate database interface (even a no-sql one) for other data.

Re:Why Django Sucks, and How we Can Fix it [slides] by singingwolfboy on Thursday September 09, 2010 @09:52AM (#1675356)
If you're going to swap out everything, are you really using Django to begin with? Why not just use TurboGears[1], which seems based on the idea of swapping out standard components?

[1] http://www.turbogears.org/

Re:Why Django Sucks, and How we Can Fix it [slides] by cageface on Thursday September 09, 2010 @11:39AM (#1675718)
Yeah, you lose the full-stack benefits of Django pretty quickly once you start swapping out components. If I wanted a more customizable Python stack I'd pick one that was designed to work that way from the beginning.
Re:Why Django Sucks, and How we Can Fix it [slides] by bsdemon on Thursday September 09, 2010 @07:08AM (#1674972)
Do you really have used Zope and Django if you say that the former is monolithic and the latter allows easy swap out its components?