5 ms·
It depends on the application. Do you care about how things work inside your database? Do you want to understand how the subsystems of your app (like authenti
by joeclark77 10y ago
It depends on the application. Do you care about how things work inside your database? Do you want to understand how the subsystems of your app (like authentication, security, the API, etc) work? Flask allows you (and forces you) to make your choices explicit. Django makes the decisions for you and hides its workings under layers of abstraction.
I can see using Django to rapidly prototype some kind of CRUD app, but on the other hand, you could just use Wordpress for that. Flask seems like it would be a superior platform for engineering anything non-trivial, especially if you care about how it works.
- odonnellryan 10y ago> I can see using Django to rapidly prototype some kind of CRUD app, but on the other hand, you could just use Wordpress for that. Flask seems like it would be a superior platform for engineering anything non-trivial, especially if you care about how it works. I feel like I'm replying a lot in this thread! I think it's the other way around. If you want to QUICKLY prototype something, use Flask: it's light weight, and your app will _literally_ be one hundred-line file + some templates. If you know you're going to use much of the common Django tools, use Django. Django projects are usually harder to spin up in my experience. I wouldn't relate Django to Wordpress at all. It'd be tough to get a Wordpress type platform from scratch in Django OR Flask.
- brianwawok 10y agoUse cookie cutter Django and just prototype in Django. Maybe 50 more lines than flask but it was a got clone not code you wrote.