The problem with CBV is the learning curve. You can do standard things like CRUD's fast as hell but if you need some kind of customisation you probably gonna need to deep dive into the class hierarchy to understand it. If you dominate it you will be very productive and happy.
I'm not saying there isn't room for improvement, there is and this blog post is showing some of them. On Tue, Mar 17, 2015 at 4:23 PM Gaurav Dadhania <[email protected]> wrote: > IMHO, Class-based views — either ones provided by Django or a 3rd party > library or your own — are an inheritance pattern, like any other design > pattern, use it if it suits your use case. Like a lot of things, there is > no one, right answer. > > I've enjoyed using CBVs for CMS-y projects (list products, product detail, > product edit OR list posts, post detail, post edit, etc.) and functional > views for endpoints which don't really have much in common eg: payment > processing, authentication/authorization endpoints, etc. (use decorators > for common simple guard checks, rate limiting, response > serialization/template rendering if you need). YMMV. > > Cheers, > G > > On Tue, Mar 17, 2015 at 8:53 PM, Asif Saifuddin <[email protected]> wrote: > >> Hi, >> >> I found this blog post about class based views of django >> >> http://lukeplant.me.uk/blog/posts/my-approach-to-class-based-views/ >> >> >> what do you guys think about? >> >> Regards >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/e84fd370-044e-456e-b2f3-fd028f41232e%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/e84fd370-044e-456e-b2f3-fd028f41232e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAHgJS%3D_OCgApx6SBdqYCQysLU6MFR%3DganAwYv7LNBE4gzzucaA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAHgJS%3D_OCgApx6SBdqYCQysLU6MFR%3DganAwYv7LNBE4gzzucaA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABqSV%3DK8c8RpYtoFCe%3Dxc2Y5rMQ7yds1qSO2yY-moWRZSYe7sw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
