Well In my opinion this is one of the things as Django community were falling behind. Asynch and Websockets are clearly gaining momentum as customer requirements for real time communication and updates is becoming a must. Therefore I wanted to point out that were missing something and an action is needed. Whether this means that as developers who <3 Django we start by contributing or set up an official group to undertake the task.
Murat On Friday, January 12, 2018 at 4:02:02 PM UTC, Andrew Godwin wrote: > > It's something like that. Django core itself is very stable and slow and > dependable, among other things, and it's still not clear even in the > industry at large how people are actually going to _use_ WebSockets and > other async-requiring things, though that is at least now improving. > > There's also a severe lack of people willing to sit down and work on this > stuff as it's super hard and I'm currently a bit burnt out on my capacity > to train up new people on it, though I'd like to get back to that point by > the end of the year. > > Andrew > > On Fri, Jan 12, 2018 at 12:07 PM, Jason <jjohn...@gmail.com <javascript:>> > wrote: > >> Andrew, what's the difference between an official Django project and >> being merged into django core? IIRC, Kenneth Reitz of requests objects to >> adding that lib to python core because of the frequency updates due to >> security patches. According to what I read, he feels (and I agree) that >> updating a package version is much easier than updating a language version, >> and allows more frequent releases. >> >> Is this similar to your thinking as well? >> >> Jason >> >> On Friday, January 12, 2018 at 1:19:37 AM UTC-5, Andrew Godwin wrote: >>> >>> Channels is not (at least in the short term) planned to be merged into >>> the Django core, but it is an official Django project. Whether it gets >>> merged in or not in the long term is a much bigger question and one I don't >>> think it's quite mature enough for yet (though Channels 2 may go a long way >>> towards making it so) >>> >>> Andrew >>> >>> On Fri, Jan 12, 2018 at 3:55 AM, Mike Dewhirst <mi...@dewhirst.com.au> >>> wrote: >>> >>>> On 12/01/2018 11:05 AM, murats...@gmail.com wrote: >>>> >>>>> Hello Django community, >>>>> >>>>> This is my first post so forgive me if this is out of context or have >>>>> been discussed already. >>>>> >>>>> I've been working with Django for many years and although have the >>>>> neccesary experience with Javascript I don't want to use NodeJS (Express) >>>>> as a backend framework because I simply really enjoy development with >>>>> Django. >>>>> >>>>> I believe that there is a growing demand within the community for >>>>> Asynchronous programming ability and Websocket support within Django >>>>> without using a mixture of Tornado, Twisted or Channels. >>>>> >>>> >>>> I believe Channels is becoming part of Django so it has been anointed. >>>> If you haven't already seen this it might answer some of you questions ... >>>> >>>> https://channels.readthedocs.io/en/latest/faqs.html >>>> >>>> Pretty much all other frameworks are offering Asynchronous support so >>>>> do we have a plan in place for this as Django Community? >>>>> >>>>> Regards >>>>> >>>>> Murat >>>>> -- >>>>> 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...@googlegroups.com <mailto: >>>>> django-users+unsubscr...@googlegroups.com>. >>>>> To post to this group, send email to django...@googlegroups.com >>>>> <mailto:django...@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/b4b641d6-1b74-4fd3-8533-8b1a7629b33d%40googlegroups.com >>>>> >>>>> < >>>>> https://groups.google.com/d/msgid/django-users/b4b641d6-1b74-4fd3-8533-8b1a7629b33d%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 users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django-users...@googlegroups.com. >>>> To post to this group, send email to django...@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/ff1fd1d3-b46c-b42d-964b-f78f353815bd%40dewhirst.com.au >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> 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...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com >> <javascript:>. >> 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/3782396c-4a80-4a57-ac9f-273bf8377764%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/3782396c-4a80-4a57-ac9f-273bf8377764%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 users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@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/a57cc1ca-75d0-47e9-bec2-971f410c129e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
