UPDATE: Django or TurboGears??
September 7th, 2009 — roaksoaxHi all!! Today I felt like I wanted to learn something new! In the past few months I’ve been doing a little Android Development. Now is time for some Web Development + python. So, what do you think I should use, Django or TurboGears, or… in such case, is there something better… what would you recommend?
Thank you!
UPDATE: Thank you very much for your comments. I’ll go with Django for now but I’ll try TurboGears later on! Thank You again!
September 7th, 2009 at 3:23 AM
I’m using Django for a project at work and enjoy it. Its quite capable and enjoyable to work with but still clearly a young project. I’d definitely use it again though.
I’ve never used TurboGears but if you do decide to try it out please be sure to post a follow up.
September 7th, 2009 at 3:47 AM
Django is _much_ simpler then TurboGears. Both in a good way, and a bad way. It’s easier to use, but you’re far more restricted in what you can do with it.
So It’s not so much a matter of which is better, but rather which tool you want to pick for which job. If you’re going to be designing multiple applications across a large enterprise. I’d say turbogears will win out 9 times out of 10 in terms of scale and feature set. But it also has a higher development cost because of that. If you’re going to stick with smaller or simpler apps, take a look at django. There’s also no reason you can’t learn both
September 7th, 2009 at 4:09 AM
Hi Andres,
You should also try out Web2Py. I quite like it. It has some very nice features. See http://www.web2py.org for details.
Released GPL2 and developed by a CS professor from DePaul Univ.
Regards
Anand
September 7th, 2009 at 5:59 AM
I’ve used both, and they are both good. Each one has a slightly different feel and features set though, so I’d use whichever “feels right”, and/or meets your specific project requirements most closely. One thing to consider though that might tip the balance is that Django has somewhat broader support from hosting companies and whatnot.
September 7th, 2009 at 7:14 AM
Hi,
As disclaimer I’d say that I haven’t used Turbogears, but had the same question 2-3 years ago and after studying both frameworks for a project, I finally decided for django as I saw turbogears as “just” a set of known python web tools glued with some sort of utilities.
I couldn’t be happier with that choice. Django has proved to be one of the most powerful and fast-evolving web frameworks. Also, the most important thing to me: it makes web development fun.
It has a steep learning curve because of its MVC model and its unique ways to do things (own templating system, etc), but once you get to it, it’s easy and fun to develop with.
Ah, also there is a lot of documentation available for django and it’s been chosen by Google as a compatible framework for their App Engine.
Well, that’s my personal opinion. I’m not saying that Turbogears is worse as I haven’t tried it, but just saying that I think you should give Django a try
Cheers,
Antonio.
September 7th, 2009 at 7:17 AM
Honestly, I would simply skip Turbogears. They used to have something there, but now it’s just become a Pylons template. I’ve personally had good experience with Django.
September 7th, 2009 at 8:18 AM
I have only used Django, but I love it!
I like the fact that I can use classes, and that django creates the database in various formats. Also the way views, models and templates are used. The way you can specify which url should load which view.
I have written a small CMS in just a day or so.
And for that one of the coolest thing was the “free” administrative backend. Just create the models and put in the config that you want a admin backend. And you get an automagically generated backend. So you can start filling the DB.
September 7th, 2009 at 10:09 AM
This is a bit emacs or vi
I haven’t used turbogears, but have used django quite a bit and loved it.
One potential plus for django is that google appengine is based on that. It uses django’s templating. So if you think you might use appengine at some point, then django is worth considering.
September 7th, 2009 at 12:00 PM
I like TurboGears more because it takes the best parts of other projects (SQLAlchemy, Pylons, all the templating engines) and allows to replace parts of the framework with relative ease. Django is pretty monolithic and contains too much magic expressions for my taste.
September 7th, 2009 at 12:48 PM
I’d recommend Django over Turbo Gears. Although it’s been a couple of years since I’ve looked at TG, I do a lot of work in both Django and RoR. I wouldn’t hesitate to recommend Django over RoR either.
September 7th, 2009 at 3:24 PM
Django.
September 7th, 2009 at 3:44 PM
Definitely Django. It makes everything so much easier. It’s just a great piece of software!
September 7th, 2009 at 3:58 PM
django + cherokee webserver
September 7th, 2009 at 6:07 PM
I like cherrypy + sqlalchemy + mako
October 3rd, 2009 at 5:41 AM
Hello,
I would like you to suggest one of the blog post regarding which technology you should use… It will help you in making decision about it
http://programminglanguagefaqs.blogspot.com/2009/10/turbogears-vs-django.html
November 11th, 2009 at 5:47 AM
I need some suggestion, our requirement is to build a site like youtube or dailymotion, which would contain tons of videos, so which one would you suggest, should i go with turbo gears or django or some else? Please let me know.
Thank you
suhail
November 19th, 2009 at 1:52 AM
@ Suhail… In my opinion you should go with Django. Django provides a simple admin interface and it is good for publishing the contents to the web like newspapers, music, videos etc.
If you need some more information about comparison of web-frameworks then here are the links for you..
http://programminglanguagefaqs.blogspot.com/2009/11/pylons-vs-django.html
http://programminglanguagefaqs.blogspot.com/2009/10/turbogears-vs-django.html
February 17th, 2010 at 4:41 PM
I recently came across one of literally hundreds of articles that weighed in on a similar debate:Django vs. Rails. I can’t seem to find it now, but they brought up one point in particular that carried a lot of weight and has definitely been a factor in a recent project of mine: Ease of use when working alongside non-programming UI/layout designers.
Django’s templating system is easily digestible by my project partner who handles the look and feel portion of the apps I work on. This factor alone has allowed us to blast through projects in record time that would have taken significantly more hand-holding from the programmer (me) had we chosen Rails, or the majority of other frameworks out there.
March 6th, 2010 at 7:34 PM
Thanks for the article. I am new at django and this got me straight.