5

Off late I've been having a lot of debate with my friend about using Flask over Django for prototyping some feature. I side with Flask, since the development time is much lesser than Django and doesn't need to follow a lot of rules.

Issue here is, I prefer flask and he prefers Django.

Need opinion on this sort of problem, where a prototype for a feature in a product has to be built. It maybe integrated into the end product, which is in Django, or may not be.

Comments
  • 1
    Thinking ahead you can go either way. Both works like a charm. But if he is comfortable is django then he should use that only
  • 1
    You can hack your way in django as fast as in flask IMHO.

    I would go with flask only when the resources are a concern (IOT)
  • 0
    @py2js both of us are comfortable with Django.
    Thanks a lot for your response.
  • 0
    @donnico resources aren't an issue here. Just which has a better turnaround time for prototyping products.
  • 0
    @ibrahmin13 if there is 10% chance that the prototype is going to grow in a project go with django
Add Comment