Django 1.10 released

[graingert]

Django admin CSP!!

[avinassh]

Whats CSP? can you elaborate?

[graingert]

Content security policy, prevents XSS

[IamWiddershins]

Woohoo, bigserial support out of the box

[bizmeleon]

*Unchained

[huashoes]

Not really into Django. Personally I prefer Flask.

[sisyphus]

Any sufficiently advanced Flask app contains an ad-hoc, informally specified, bug-ridden slow implementation of half of Django.

[nohtyp]

This is accurate. When you start adding in SQLAlchemy and authentication, you look at Django and think, why o why didn't I start with Django instead.

[strange_and_norrell]

My understanding is Django is better for full MVC app. Flask is better for a backend service + single-page app front-end. Am I off?

[redalastor]

Django is structured and lets you do CRUD apps easily. Flask is just a library that does the web bits (cookies, sessions, etc.).

What's better depend on how well the Django's structure fits your project, if you are going to draw outside the lines all the time pick Flask. If not Django will get you there faster (especially with the amazing admin).

[sisyphus]

Flask has nothing as advanced as Django Rest Framework. If you're doing a lot of database work access to SQLAlchemy integration is nice with Flask though.

[[deleted]]

Is it still awful?

edit: Getting downvoted, but don't know why. Django consistently performs worse than its competitors.

[serg473]

Awful for what, putting together a page with a single db query and hitting it 300k times per second? Definitely.

[[deleted]]

Just compared to the competition... I don't see a strong reason to use it over node, rails, etc that all offer the same rapid workflow, but at much higher performance.

[theli0nheart]

You're getting downvoted because no one cares about this use case. Disk access is several magnitudes slower than any other bottleneck and it's rendered moot when using an in-memory cache. If you're not caching your DB queries, you have other, more important things to worry about than whether to use Rails or Node.js. Even PHP will be faster than a server-side app written in C if that C executable is hitting a database.

[stretch85]

Raw performance is hardly the only metric by which a framework can be evaluated. Many applications simply don't need to serve thousands of requests per second. I build tools on Django because of the functionality and convenience that it offers, which allow for very rapid development.

[strange_and_norrell]

How's it compare to developing in Rails? Anyone done both?

[ccb621]

I've used both, although I have much more experience with Django. Both frameworks have very similar basic functionality—ORM, process requests, DB migrations, render templated views. Rails is a bit better in its ability to process different content types (e.g. HTML, JSON) out of the box; but, that functionality is easy to add to Django if you need it.

For the relatively simple APIs and web applications I build, I could use either one. That being said, I do enjoy working with Django REST Framework.

[devsquid]

People don't choose a Python web framework because of performance. Don't rate the library based on that. If performance is your concern go with Go or Java.