> I would like to hear > somebody who has this knowledge. Well, I think TurboGears and Django are both great frameworks, so you won't "go wrong" no matter which one you choose. That said, you're asking on a TurboGears list, and I'm the author of a TurboGears book, so perhaps you won't get an "unbiased" opinion out of me.
I think TurboGears provides better templating solutions, a better Object Relational Mapper, and easier URL-controller mapping. Django on the other hand offers a fantastic "Admin interface" which can help you get content managment type applications up and running very, very quickly. TurboGears provides more support for Ajax, and is generally focused more on the "application" side of web development, whereas Django has a historical focus more on the "dynamic content" side of the web. Of course there's no firm line between an web application and a site with dynamic content, and both frameworks have been successfully used for both kinds of sites. In the end it all boils down to which one works for you, which style of web development fits your needs. Another thing which I should mention is that TurboGears tends to be somewhat more forward looking of a place than Django, so there's likely to be access to new python technologies like SQLAlchemy in TurboGears before you'll ever see it in Django. This can be a good thing, because SQLAlchemy is awesome, and makes lots of hard problems easier. But it can be a bad thing because Django's monolithic form and central control structure ought to make version to version upgrades a bit easier by preventing API changes. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
