Re: Django to serve JSON: overkill?

Hi Charley,

You should not regret this choice.

Sometimes Django seems a bit overkill at the first glance. But most of the times, once the project has made some progress you'll quickly appreciate the fact it is like Python : batteries included. No need to hunt for external add-ons which will integrate more or less easily when it comes to take care of CORS, CSRF, sessions, I18N,... All is already here for free. I could verify this on a Flask based project : you're left alone when time comes for you to find the right LEGO blocks and make then fit together. Django creators have already made this for you, and they're very smart people.

And of course the default Django configuration can be optimized by removing middlewares and features you don't need to cut it down to the strict necessary. So, why bother ?

Regards

Eric

---

From: django-users@googlegroups.com <django-users@googlegroups.com> on behalf of Charley Paulus <charley.paulus@gmail.com>
Sent: Sunday, October 28, 2018 2:53:04 PM
To: Django users
Subject: Re: Django to serve JSON: overkill?

 

Hi Eric,

Yes that helps a lot.
I have data models and related DB.
I'll go with Django.

Thanks.

Best regards,
Charley

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/77c35a21-591d-41e5-8bd5-4314a5b0614d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.