News for hackers. Stuff that matters.
Re:Django 4.1 by nilsbunger on Wednesday August 03, 2022 @10:29AM (#32332190)
> If I was running a trading clearing house, or Instagram, I'd probably care about marginal improvements, and then use another language.

Ha, Instagram was written in Django!

Re:Django 4.1 by Demiurge on Wednesday August 03, 2022 @11:22AM (#32332972)
Thats why I mentioned it, lol. I figured a few percentage points improvements in perf for Instagram == $$$
Re:Django 4.1 by collinmanderson on Wednesday August 03, 2022 @10:41AM (#32332399)
Right, though they're stuck on 1.8 (upgraded to 1.8 only so they could use python3), and really just use it for request/response/views, not ORM or anything else.
Re:Django 4.1 by throwaway_4ever on Thursday August 04, 2022 @08:34PM (#32350106)
Are they using DRF? Because obviously mobile app can't use templates and Django doesn't default support REST endpoints, does it?
Re:Django 4.1 by collinmanderson on Friday August 05, 2022 @09:11AM (#32355595)
> Django doesn't default support REST endpoints, does it?

You just have to manually call json.parse(request.body) for incoming requests and return JsonResponse(data). And you generally need to serialize the data yourself.

Django does have some built-in model serialization, but that's mostly for import/export data, not really for sending to the browser.