Not at all, just that Cython itself is probably not the approach to take. Andrew Godwin recently posted a proposal for a Django ASGI roadmap <https://groups.google.com/forum/#!topic/django-developers/Kw7-xV6TrSM> and there's a good amount of work to be done there.
Benchmarks have their place. But if they're not matching real world problems, then I don't see much use of them other than stroking egos of their developers. And my personal experience says that most of the problems with Django's slowness have most of the bottlenecks with db connections, networking latency and other things outside of Python. And those problems inside Python might not be the best things to leverage Cython for. I get the issue of wanting to show up to your peers with node, but personally, I just don't find it worth it. It has its use cases, but more and more I see it being squashed into a use case its really not suited for simply because the creator or team are very one-dimensional as far as languages.. Use the right tool for the job, and just ignore the fanbois. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3a82c5de-b3d0-449a-8e6b-2f008fd9c803%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.