3 ms·
I am obviously biased, as I run a django development company. That said, Ill start with answering the drawbacks of Django, 1. Learning curve. Not more than an
by shabda 17y ago
I am obviously biased, as I run a django development company. That said, Ill start with answering the drawbacks of Django,
1. Learning curve.
Not more than any other framework. Plus the Documentation is top notch. (The documentation was what sold me when I was evaluating.)
2. Smaller community
Definately true. But beyond a critical size, size of community does not matter. Django is well above that size. (Irc: any given time ~200 Devs. Google group: 14000+ Users )
3. Slower development cycle of the project itself?
Why? If you give more details, I can answer that.
4. (un)Availability of offshore resources
Definately less than Rails, but still not as bad as you would have thought. A very small list, http://uswaretech.com/blog/2009/03/web-development-companies-working-with-django/ http://uswaretech.com/blog/2009/03/web-development-companies...
Thats said, given the information you have, I your case I would choose Rails. Even if most of the work you are looking to offshore, your existing Rails experience would be a huge plus, helping you evaluate vendors, keep track.