April 22, 2008
Very good introductory article. Our company has deployed a number of Django sites over the past couple of years and all of the advantages Dan points out (quick to deploy, admin tool, etc) helped get us moving faster than if we had chosen another language/framework. From a business perspective, however, we’ve had a number of challenges with Django:
1. While much of the admin tool gets built automatically, the usability can be horrendous. We saved a significant amount of time upfront when launching the sites, but we quickly lost all that ground and more in the extra clicks, scrolls, and other functions. We’re in the magazine business so the admin is in use all day every day. Ultimately we can shape the admin to address these concerns but then we’ve spent the same amount of time as if we had architected a proper admin tool from the beginning.
2. Finding Django developers has been very difficult so the time spent on recruitment and training has been a liability.
3. Django hasn’t reached version 1.0 yet so we’re dealing with legacy versions without a timeline for rolling out the full version.
All in all, as a framework, I would agree with the author on the advantages outlined but if we had to do it all over again, I would bypass Django in favour of something more established simply for the impact on day-to-day business.