merge ApiView and GenericAPIView

[deronnax]

I struggle to see the purpose difference between the two. The naming itself conveys the lack of distinction between the two (ask a stranger what is the difference in role between the APIView and the GenericAPIView, according to their name).
Moreover, APIView is only inherited by GenericAPIView, reinforcing the feeling that the split between the two makes no sense.
I strongly think the two should be merged.

[browniebroke]

I think the main distinction is that GenericAPIView assumes to work with a model / queryset while the base APIView is not. I've used APIView to implement more custom stuff which don't map directly to a model: a proxy endpoint calling an 3rd party service with a secret key behind user auth.

I think having them separate gives the option to the user to opt to the more bare option when they need to.

[deronnax]

If that's so, renaming it ModelAPIView or QuerySetAPIView would IMHO be huge win. The purpose would be immediately identifiable.