News for hackers. Stuff that matters.
Re:Why I switched to Pylons after using Django for six months by idan on Monday March 08, 2010 @06:45PM (#1176896)
It seems like a lot of people get frustrated with Django because it isn't the Framework for Copy & Paste Coders Who Like to be Spoonfed.

To some degree, this is a failure of the Django community's messaging. Django is highly modular and, if anything, disassembles gracefully as you start running into more complex scenarios (even more so in 1.2 than 1.1).

It's best to think of Django as a robust set of wheels you don't have to reinvent for each new site you build, and a toolkit for building new wheels you can not-reinvent next time around.

All of the above is painfully obvious to anybody who has spent a decent amount of time with Django, but might not be so clear to somebody just finding their way or using Django in a limited fashion. I'm sad to see that somebody had a poor experience with Django, but this post is basically a lot of whining about an inability to figure things out and use the framework as intended.

Re:Why I switched to Pylons after using Django for six months by mgrouchy on Monday March 08, 2010 @07:23PM (#1176982)
I think your sentiment here is pretty correct. We have been using Django to build SWIX ( http://www.swixhq.com ) and for the most part we find Django to be a blessing. It does much of the heavy lifting and helps us keep all our code modular and loosely coupled(at least when we are doing it right).
Re:Why I switched to Pylons after using Django for six months by enjo on Monday March 08, 2010 @08:10PM (#1177123)
I concur.

I've built one very complex site using Django, and it's worked great.

For the authors specific complaints:

- We found a nice reusable app. for recpatcha that basically just boils the whole thing down to a form field. It works flawlessly. - I implemented twitter/facebook connect integration with no issues (all using the standard auth system, and two apps) - We've done things like dynamic custom forms that work just beautifully.

It's a pretty long list of things that we've been able to accomplish with Django. We're really happy with it, particularly since the 1.1 release. It has a ton of flexibility, while still virtually automating most of the things we do often.

It's certainly not turn-key, but we've done this without modifying one line of django code.

In the near future I'm hoping to be able to take some time to open source some of this work.

Re:Why I switched to Pylons after using Django for six months by vanschelven on Monday March 08, 2010 @07:11PM (#1176955)
I'm not too sure models disassemble too gracefully. I can't really take my own app, subclass a model and modify a field, to name just an example.
Re:Why I switched to Pylons after using Django for six months by thomaspaine on Monday March 08, 2010 @09:15PM (#1177271)
Re:Why I switched to Pylons after using Django for six months by enjo on Monday March 08, 2010 @10:51PM (#1177424)
For other cases (Where you don't want to create a new model, just change it's behavior) proxy models are incredibly useful.

http://docs.djangoproject.com/en/dev/topics/db/models/#id8

Re:Why I switched to Pylons after using Django for six months by stevenwei on Tuesday March 09, 2010 @05:36PM (#1179582)
Spoonfed? No.

Would I like commonly repeated problems to be solved elegantly so I can easily integrate them into my project without digging through poorly documented source code? Yes.