News for hackers. Stuff that matters.
Re:Django Newbie Mistakes by jojo64 on Friday June 29, 2018 @02:46AM (#17422858)
Well we can migrate to python 3 but this will be more investment in a stack that is more and more obsolete (Django) for SPA. Developers need also to learn the new best practices for python 3. At the end this will result in short term with python 3 code base written in python 2 style without the benefits of typing etc. Investment without benefits except keep our stack up-to-date.

Each solution for Python/Django add complexity: - async -> celery/rabbitmq - websocket -> Channels, Daphne, asgiref, channels_redis, redid.

It's quite huge to manage.

Re:Django Newbie Mistakes by collyw on Friday June 29, 2018 @10:23AM (#17424675)
Django obselete?

Sure....

Re:Django Newbie Mistakes by jojo64 on Friday June 29, 2018 @12:57PM (#17425771)
For our usage that's my point of view. When you need to manage ws & asynchronous task, you are just ending stacking technologies to make Django enter in 2018 (remember tornado?). I would say that the framework didn't followed technology evolution and so our new requirements

For old good stuff is still a good framework. It really depends on your usage.