Re:Django REST framework 3.1 released
by mcescalante on Friday March 06, 2015 @12:28PM
(#9158234)
I am writing an API right now in Flask, and I chose it over Django never having used Django for a REST service before.
When you say "there's no story" around auth, endpoint versioning, and other things does that just mean that you're not forced to follow those conventions with Flask / that Django offers utilities to help? I am a bit confused/curious what you meant by that since I've seen some wonderful Flask auth work, and endpoint versioning is pretty standard on most APIs, but seems like Django is a bit more strict with what they want you to do.
Re:Django REST framework 3.1 released
by tallerholler on Friday March 06, 2015 @12:53PM
(#9158390)
strict in what way? I've built many api's using django-rest-framework and it is truly awesome to work with, completely extensible and flexible and never seems to get in my way
Re:Django REST framework 3.1 released
by mcescalante on Friday March 06, 2015 @01:24PM
(#9158566)
I just meant that they offer more of a base + guidelines for you to work with when compared to Flask's "roll it yourself" approach to REST.
Re:Django REST framework 3.1 released
by chucksmash on Friday March 06, 2015 @11:26AM
(#9157828)
We're not building from scratch. The constraints imposed by the pre-existing stuff mean we can't really take full advantage of the upsides of Django.
There are a hodge-podge of plugins to do various things, but they don't necessarily share the same design principles or work well together. Some are so abstracted that by the time you've got a concrete implementation you could have just rolled your own.
EDIT: Grammar, added a sentence.