Re: Will function based views ever be deprecated?

> I've just re-read my message and notice that it is extremely aggressive. I
> want to apologies for that. When I typed it I had just had a big argument with
> someone and it came across in my message to this list. That was uncalled for
> and I'm not normally that type of person. So sorry again.
Hello,

I don't think you need to apologize. Your message was a bit agitated perhaps,
but I wouldn't call it aggressive. Agitated is fine—it goes straight to the
pain. I also liked the ensuing discussion, and I guess many people did, because
seeking the ideal structuring of the code is an endless quest.

Regards,

A.

Antonis Christofides
http://djangodeployment.com


On 04/03/2017 01:35 PM, Some Developer wrote:
> On 02/04/2017 04:37, Some Developer wrote:
>> Hi,
>>
>> I was wondering if function based views will ever be deprecated? I
>> absolutely hate class based views with a passion for various reasons
>> (too complex, trying to solve a problem that doesn't exist etc). With a
>> function based view I can write it in 2 minutes pretty much and handling
>> multiple forms on the same page is a piece of cake. The same is not true
>> of class based views. You need to look up which classes a certain class
>> based view inherits from to see what methods are available, handling
>> multiple forms on the same page is a pain in the arse if not impossible
>> and various other things that are just way more difficult than they
>> should be.
>>
>> So yeah. Are function based views ever going to go away? I've already
>> noticed that in Django 1.11 the login() and logout() functions are going
>> away in favour of class based views which seems silly as I'll have to
>> rewrite my perfectly working user app to use class based views now.
>>
>> Is that a sign of things to come? If that is what the developers are
>> planning can I please beg them to reconsider? Function based views are
>> just fine. You might prefer class based views but there are users out
>> there who much prefer function based views.
>>
>> Please don't take this as an aggressive post. I love working with Django
>> and I'm just passioniate about it. This isn't a flame post.
>>
>> Thank you for any help :).
>>
>> Some Developer.
>
> Hi,
>
> I've just re-read my message and notice that it is extremely aggressive. I
> want to apologies for that. When I typed it I had just had a big argument with
> someone and it came across in my message to this list. That was uncalled for
> and I'm not normally that type of person. So sorry again.
>
> If I post again I'll make sure to only do it when I am nice and happy :).
>
> Some Developer.
>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/17e50dbf-0b40-12ec-f9f4-02a36b9d71a0%40djangodeployment.com.
For more options, visit https://groups.google.com/d/optout.