Eighteen months of Django

#1

Post by dangoldin » Tue, May 07, 2013, 9:38 PM UTC

Re: Eighteen months of Django

#2

Post by tesmar2 » Tue, May 07, 2013, 9:55 PM UTC

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

Re: Eighteen months of Django

#3

Post by dangoldin » Tue, May 07, 2013, 10:02 PM UTC

tesmar2 wrote: post #2

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

I think it really depends on what the project is.

If it's relatively simple and you don't really want to deal with user registration/databases I'd say definitely go with Flask. Django does a pretty good job of those two but until it "clicks" you end up being confused.

Re: Eighteen months of Django

#4

Post by jspiral » Tue, May 07, 2013, 10:03 PM UTC

nice summary, sent to a colleague who is starting with django.

Re: Eighteen months of Django

#5

Post by dangoldin » Tue, May 07, 2013, 10:05 PM UTC

jspiral wrote: post #4

nice summary, sent to a colleague who is starting with django.

Glad to have helped. If he/she has any questions you can have them reach out to me. I'm definitely not an expert but can offer some suggestions. dangoldin gmail is the email.

Re: Eighteen months of Django

#6

Post by ioddly » Tue, May 07, 2013, 10:05 PM UTC

tesmar2 wrote: post #2

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

I suppose it depends on what your goals are. If your goal is just to crank out some Python, I'd go with Flask (or my personal favorite Bottle).

Re: Eighteen months of Django

#7

Post by aartur » Tue, May 07, 2013, 10:09 PM UTC

tesmar2 wrote: post #2

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

If you are new to Python and just want to have a working project instead of tinkering, then Django is better suited. Flask is for more advanced uses where you need to have more control or be able to integrate components you choose (like SQLAlchemy instead of Django ORM, or a NoSQL DB).

Re: Eighteen months of Django

#8

Post by hamax » Tue, May 07, 2013, 10:09 PM UTC

tesmar2 wrote: post #2

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

I really like Flask but I still go with Django when I need the admin.

Re: Eighteen months of Django

#9

Post by aartur » Tue, May 07, 2013, 10:21 PM UTC

dangoldin wrote: post #3

tesmar2 wrote: post #2

As someone who is thinking about doing a python project, should I learn Django or just go with Flask? Any thoughts on those two?

I think it really depends on what the project is. If it's relatively simple and you don't really want to deal with user registration/databases I'd say definitely go with Flask. Django does a pretty good job of those two but until it "clicks" you end up being confused.

Funny that I wrote that Flask is for advanced usage and you wrote that Flask is for simple usage. If the project is really simple - no database, no declarative forms etc. - then Flask will be better. But if you go to "medium complexity" Django gives you ready components which you need to integrate in Flask (SQLAlchemy, WTForms etc.). You also need to invent your own project structure, and Django already has a hardcoded one. When the project complexity is "high" then Django starts to be too limited/"hardcoded" and flexibility/minimalism of Flask starts to shine.

Re: Eighteen months of Django

#10

Post by dangoldin » Tue, May 07, 2013, 10:26 PM UTC

aartur wrote: post #9

dangoldin wrote: post #3

Earlier quoted context omitted.

I think it really depends on what the project is. If it's relatively simple and you don't really want to deal with user registration/databases I'd say definitely go with Flask. Django does a pretty good job of those two but until it "clicks" you end up being confused.

Funny that I wrote that Flask is for advanced usage and you wrote that Flask is for simple usage. If the project is really simple - no database, no declarative forms etc. - then Flask will be better. But if you go to "medium complexity" Django gives you ready components which you need to integrate in Flask (SQLAlchemy, WTForms etc.). You also need to invent your own project structure, and Django already has a hardcod…

Haha yea you're right! Funny how my bias trickled through. I haven't done too much Flask customization and only use it for the one off simple project that just need a web interface.

Django is definitely more in the range of "we want you to write" this way but I've found it to be at least a bit more customizable than RoR. Flask is on the other extreme which lets you do whatever you want.. but you're the one who has to do it.