5 ms·

There was a port of DRF for Flask, but it was not as mature and not as good. I went with Django mainly because of the included batteries and in particular DRF.

by harel 10y ago

overcast 10y ago
I was just always dissuaded from the size of Django, Flask is mininal, and gets up and running quicker for me. Coming from a lot of Express work, it just made more sense to me, but I'll be definitely diving into DRF for my new project.
- kennydude 10y ago
  Django is batteries-included, but the batteries aren't heavy. You can easily turn off 99% of the stuff it does for you. You also never know when you need a really good admin panel.
  - collyw 10y ago
    The admin is great, especially at the start of a project, when you want to look at and manipulate your data even if it isn't needed in the product you end up with.
- harel 10y ago
  The size is less relevant - you only use what you need. The other main reason I chose Django for a particular project is the ease at which I can find experienced developers afterwards. Not that it really matters that much, Python being Python, but its easier to find someone with Django experience than one with Flask.
  - morenoh149 10y ago
    But django is a superset of Flask. If it's easy to find django devs it must be easy to find Flask devs.
    - harel 10y ago
      Not really. Because its python, its all Python devs. But if you want someone with specific Django experience, you'll find it easier to find than flask. Popularity wins and Django is popular (for a good reason)
- justinsaccount 10y ago
  I use flask for a few applications.. it works, but even in my cases: Any sufficiently complicated flask application contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of django. For sites that are just a few endpoints, it's great. I use it on an application that uses redis+gearman to spawn docker containers on demand. django would have worked too, but I'm not using anything other than routing and templating. On the other hand, I have an application that I built on flask that I needed to shift the timezone of the dates. in django you change TIME_ZONE and you're done. My flask app I had to fix it all myself, it was a nightmare.
- Spiritus 10y ago
  Django can be minimal if you want: https://github.com/rnevius/minimal-django/blob/master/minimal.py https://github.com/rnevius/minimal-django/blob/master/minima...
- ralmidani 10y ago
  The size of the framework is really not relevant in the context of Python server-side development. You just import what you need and ignore what you don't. For example, I develop single-page apps with Django+DRF and Ember, so I never use Django's template engine. If you really want to minimize your setup, you can even go into your settings.py file and turn off the middleware you don't need. Put another way, it's not like client-side JavaScript where the entire framework is sent to the user's browser.

There was a port of DRF for Flask, but it was not as mature and not as good. I went with Django mainly because of the included batteries and in particular DRF.

by harel 10y ago

There was a port of DRF for Flask, but it was not as mature and not as good. I went with Django mainly because of the included batteries and in particular DRF.

overcast 10y ago

I was just always dissuaded from the size of Django, Flask is mininal, and gets up and running quicker for me. Coming from a lot of Express work, it just made more sense to me, but I'll be definitely diving into DRF for my new project.

kennydude 10y ago
Django is batteries-included, but the batteries aren't heavy. You can easily turn off 99% of the stuff it does for you. You also never know when you need a really good admin panel.
- collyw 10y ago
  The admin is great, especially at the start of a project, when you want to look at and manipulate your data even if it isn't needed in the product you end up with.
harel 10y ago
The size is less relevant - you only use what you need. The other main reason I chose Django for a particular project is the ease at which I can find experienced developers afterwards. Not that it really matters that much, Python being Python, but its easier to find someone with Django experience than one with Flask.
- morenoh149 10y ago
  But django is a superset of Flask. If it's easy to find django devs it must be easy to find Flask devs.
  - harel 10y ago
    Not really. Because its python, its all Python devs. But if you want someone with specific Django experience, you'll find it easier to find than flask. Popularity wins and Django is popular (for a good reason)
justinsaccount 10y ago
I use flask for a few applications.. it works, but even in my cases: Any sufficiently complicated flask application contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of django. For sites that are just a few endpoints, it's great. I use it on an application that uses redis+gearman to spawn docker containers on demand. django would have worked too, but I'm not using anything other than routing and templating. On the other hand, I have an application that I built on flask that I needed to shift the timezone of the dates. in django you change TIME_ZONE and you're done. My flask app I had to fix it all myself, it was a nightmare.
Spiritus 10y ago
Django can be minimal if you want: https://github.com/rnevius/minimal-django/blob/master/minimal.py https://github.com/rnevius/minimal-django/blob/master/minima...
ralmidani 10y ago
The size of the framework is really not relevant in the context of Python server-side development. You just import what you need and ignore what you don't. For example, I develop single-page apps with Django+DRF and Ember, so I never use Django's template engine. If you really want to minimize your setup, you can even go into your settings.py file and turn off the middleware you don't need. Put another way, it's not like client-side JavaScript where the entire framework is sent to the user's browser.