Abandon Class-Based Views or give a warning about their use

[treyhunner]

Some of the discussion I had with Django/web programming newbies during the talk led me to believe that the class-based views that were discussed may have made the presentation more confusing than using plain function-based views.

Luke Plant, one of the Django core devs, has written two blog posts in the past on his dislike for CBVs:

• Class Based Views and DRY Ravioli
• Django's CBVs were a mistake

Regardless of whether we demonstrate the use of CBVs we should probably warn about their downsides (mostly that it's often difficult to break free from their rigid purposes without writing confusing code (ravioli code as Luke and others call it).

[davidfischer]

I'm ok with that. I hadn't really done CBVs before this presentation so I could go for sticking with function-based views. I think showing fewer options (at least initially) is better and we have to show FBVs.