I don&#x27;t think this is really the right medium to ask that question. You&#x27;ll find certain topics (Golang, Django, Unicorns) get up voted heavily on Hacker news and I think this indicates a bias that&#x27;ll hurt discussions like yours.<p>That said I&#x27;ll take a stab with it, as I&#x27;ve worked with both. First off they&#x27;re both MVC frameworks that prioritize a fast, convention-first, development cycle. They both are very well proven, they both have great documentation, and they both have a large number of resources detailing nearly every aspect of their deployment.<p>So for me it is really a question of these three things:<p>* what your team is used to<p>* what resources (capital to buy talent if need be, time to invest in research, etc.) are available to you<p>* what edge-cases your app might come across over the development cycle (do you need real-time features? might you use a niche data-store? do you have to connect with particular third-party services?)<p>For each of those points you need to do some planning and decide what the answer if for your team. I believe if you have a grasp on this the answer will be some what evident to you. If it&#x27;s not, then I think you can just flip a coin because it won&#x27;t matter to you.