Django REST framework 3.1 released • Hacker News Board

Re: Django REST framework 3.1 released

#41

Post by danielsamuels » Fri, Mar 06, 2015, 8:17 PM UTC

jnbiche wrote: post #4

Just wanted to say that this is one of the most beautifully-documented projects I've ever used. Bravo!

Perhaps, but it's definitely wrong in places. I was working with a project this afternoon and the examples given didn't actually work. I should definitely take some notes on which bits were wrong, as it would be useful to have them fixed.

Re: Django REST framework 3.1 released

#42

Post by jsmeaton » Fri, Mar 06, 2015, 8:23 PM UTC

chucksmash wrote: post #20

brento wrote: post #16

Earlier quoted context omitted.

I'm curious why the choice was made to switch to Flask?

We use both. I came in with a preference for Django but the applications we build are generally talking to legacy data stores so we more or less lose the Django ORM right off the bat. That cancels out a lot of the advantages Django has, unfortunately.

We use Django for legacy databases, both as a readonly way to access data in a managed data warehouse and to replace an application that had not the nicest schema to begin with. Routers to the rescue.

Of course if the database you're working with is a shambles, then you're going to have a bad time.

Re: Django REST framework 3.1 released

#43

Post by papa_bear » Fri, Mar 06, 2015, 8:35 PM UTC

Anyone have any thoughts on DRF vs Tastypie?

I've been using tastypie for the past few months in a project and I'm kindof regretting it - I'm finding some of the design decisions hard to understand and not super well documented. But I've gotten to the point where I'm using it in production and it feels like it might be too big of a pain to switch at this point.

Re: Django REST framework 3.1 released

#44

Post by macavity23 » Fri, Mar 06, 2015, 8:48 PM UTC

papa_bear wrote: post #43

Anyone have any thoughts on DRF vs Tastypie? I've been using tastypie for the past few months in a project and I'm kindof regretting it - I'm finding some of the design decisions hard to understand and not super well documented. But I've gotten to the point where I'm using it in production and it feels like it might be too big of a pain to switch at this point.

I find DRF far superior. Nice consistent API once you get the hang of views and serializers, and the built-in browser UI is just awesome.

Re: Django REST framework 3.1 released

#45

Post by ralmidani » Fri, Mar 06, 2015, 8:55 PM UTC

papa_bear wrote: post #43

Anyone have any thoughts on DRF vs Tastypie? I've been using tastypie for the past few months in a project and I'm kindof regretting it - I'm finding some of the design decisions hard to understand and not super well documented. But I've gotten to the point where I'm using it in production and it feels like it might be too big of a pain to switch at this point.

I'm not an expert, but from what I've read of the docs of both projects I understanding DRF is more modular and easier to customize with its Serializer, Parser, View, Viewset, etc. classes than Tastypie with its monolithic Resource class.

Re: Django REST framework 3.1 released

#46

Post by johnthedebs » Sat, Mar 07, 2015, 6:17 AM UTC

chucksmash wrote: post #20

brento wrote: post #16

Earlier quoted context omitted.

I'm curious why the choice was made to switch to Flask?

We use both. I came in with a preference for Django but the applications we build are generally talking to legacy data stores so we more or less lose the Django ORM right off the bat. That cancels out a lot of the advantages Django has, unfortunately.

In case you didn't know, you can have Django auto-generate models from existing databases. I've used it a couple times and it worked very well.

Relevant docs: https://docs.djangoproject.com/en/1.7/howto/legacy-databases...