Adam Gomaa explains why I prefer Django to Turbo Gears
I’ve built a couple of small web projects using Turbo Gears and Django. I found the Django experience much nicer, in the end, and am sticking with it for now. My main beef with Turbo Gears is that to figure out how to do anything I had to visit 3-4 different web sites to read documentation for the different pieces. The larger problem, as Adam Gomaa points out in his post about Pylons and Django, is that Turbo Gears lacked conceptual integrity.
“The ‘best tool for the job’ almost always consists of ‘the most easily maintained tool for the job,’ which itself correlates strongly with ‘what comes out the box.’ The fewer pluggable, add-on, additional-setup-required components there are, the better. Two templating languages is not a feature, it’s a mistake. Four? That’s a nightmare.”
That nails it pretty succinctly. I don’t love working with Django.
They are slow to release new versions (even compatible versions) and I’ve recently had to start tracking the trunk in order to build the site I’m working on now (ugh). But at least all of the documentation is in one place, and the various layers work together consistently.