Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>[Repost from HN, same link as question, as I would like to hear your(you did not reply on HN) and SO response.]</p> <p>I am obviously biased, as I run a django development company. That said, Ill start with answering the drawbacks of Django,</p> <ol> <li><p>Learning curve.: Not more than any other framework. Plus the Documentation is top notch. (The documentation was what sold me when I was evaluating.)</p></li> <li><p>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 )</p></li> <li><p>Slower development cycle of the project itself?: Why? If you give more details, I can answer that.</p></li> <li><p>(un)Availability of offshore resources: Definately less than Rails, but still not as bad as you would have thought. A very small list, <a href="http://uswaretech.com/blog/2009/03/web-development-companies" rel="nofollow noreferrer">http://uswaretech.com/blog/2009/03/web-development-companies</a>...</p></li> </ol> <p>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.</p> <p>On a semi-related note, Django is less mature/smaller community is way overblown, some figures,</p> <ol> <li>Years under development. ROR: 5/Django 5</li> <li>Members in largest google group: ROR 18000+/Django 14000+</li> <li>Members in Irc currently: Ror 436/Django 401</li> <li>Commits to repo: Ror ?/Django 11000+</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload