Rendered at 09:04:58 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
stuaxo 6 minutes ago [-]
Nice.
I've been meaning to do my own Django post, on some other bits we take for granted - I should do it.
People should be using Django, the best parts are so useful you don't notice them until you switch platforms and implement them badly.
Every app that used a more narrow solution ultimately ends up implementing parts of Django badly.
The best way to solve this from Djangos side would be to have official ways of:
- Using the ORM outside of Django
- Doing single file Django apps
Both of these have various 3rd party solutions, which shows demand.
In the past other bits of Django have been split off by 3rd parties but those two are the places to start.
JodieBenitez 35 minutes ago [-]
Most loved feature, for me: No dramatic changes, just sane and careful evolution.
cryo32 6 minutes ago [-]
My favourite part of Django is it's not Rails :)
tonyedgecombe 12 minutes ago [-]
I haven’t used Django for a long time but when I did I found it one of the best documented projects out there.
Maxion 30 minutes ago [-]
Django is boring, which is why it works well. Use the ORM together with DRF serializers and an OpenApi generator and you can create TS types and TS client directly from your API.
Works incredibly well almost straight out of the box for even quite large applications. Once you start to grow out of it, it's easy to bypass the ORM and write raw sql queries.
You also won't be re-writing your backend every few years, the cost of which techbros often ignore.
stavros 42 minutes ago [-]
I agree, Django is just fantastic. Nothing is perfect, but Django is just really well-designed, with components that fit together naturally into a balanced whole.
weatherlite 34 minutes ago [-]
Just wanted to say I saw your last stand up , you're hilarious!
stavros 33 minutes ago [-]
Thanks, my love of comedy is only surpassed by my love of Django.
I've been meaning to do my own Django post, on some other bits we take for granted - I should do it.
People should be using Django, the best parts are so useful you don't notice them until you switch platforms and implement them badly.
Every app that used a more narrow solution ultimately ends up implementing parts of Django badly.
The best way to solve this from Djangos side would be to have official ways of:
- Using the ORM outside of Django - Doing single file Django apps
Both of these have various 3rd party solutions, which shows demand.
In the past other bits of Django have been split off by 3rd parties but those two are the places to start.
Works incredibly well almost straight out of the box for even quite large applications. Once you start to grow out of it, it's easy to bypass the ORM and write raw sql queries.
You also won't be re-writing your backend every few years, the cost of which techbros often ignore.