News for hackers. Stuff that matters.

A comment on Django 2.0 released. Parent comment

Re:Django 2.0 released by jrs95 on Saturday December 02, 2017 @12:16PM (#15832855)
It's not inherently async, but it supports async. Although database support for that isnt great, so I'd recommend just sticking to synchronous stuff for now unless you don't mind using raw SQL.

If it were me, I'd probably use something else before I tried to squeeze that much performance out of Python at this point to though. I hope library support catches up and it becomes more convenient, but I don't think a predominantly synchronous ecosystem has really successfully transitioned to async before.

[ Parent | on HN ]
Re:Django 2.0 released by mattgreenrocks on Saturday December 02, 2017 @12:47PM (#15833020)
AFAIK, C# navigated the sync-async transition well. Admittedly, this is a function of time, as it has had async/await for quite awhile.
[ Parent | on HN ]
Re:Django 2.0 released by jrs95 on Saturday December 02, 2017 @01:50PM (#15833311)
Totally forgot about that one. Having nearly everyone on one the same framework probably helped a lot with that. I don't think anyone else really has that advantage. Except maybe Ruby and Rails... Perhaps some good concurrency stuff will come of Ruby 3.
[ Parent | on HN ]