I've never understood why people like this framework so much. It's not that flexible. If you want to customize your API in specific ways ( ordering, nested resources, validation ), then you will undoubtedly just write your own CBV(s).
After writing your own CBV(s) for awhile, you will either love that solution or hate it and look for something more flexible and out-of-the-box.
For many of the things that Django REST framework version 3 is attempting to solve there is already an awesome alternative to it and TastyPie called Conduit. I highly recommend people give it a shot, since it's pretty modular. It also presents a different alternative to Function and Class-Based views:
http://django-conduit.readthedocs.org/en/latest/
After writing your own CBV(s) for awhile, you will either love that solution or hate it and look for something more flexible and out-of-the-box.
For many of the things that Django REST framework version 3 is attempting to solve there is already an awesome alternative to it and TastyPie called Conduit. I highly recommend people give it a shot, since it's pretty modular. It also presents a different alternative to Function and Class-Based views:
http://django-conduit.readthedocs.org/en/latest/