←back to thread

Happy 20th Birthday, Django

(www.djangoproject.com)
578 points davepeck | 3 comments | 13 Jul 25 18:44 UTC | HN request time: 0s | source
Show context
Euphorbium ◴[14 Jul 25 12:55 UTC] No.44559640[source]▶
Fastapi has completely replaced django for me. I do not miss orm at all.
replies(3): >>44559711 #>>44559962 #>>44561110 #
lutoma ◴[14 Jul 25 13:26 UTC] No.44559962[source]▶
I’ve also switched away from Django (to Litestar), but the ORM is the mean thing I keep missing from Django. SQLAlchemy feels really clunky by comparison
replies(2): >>44561669 #>>44562230 #
1. sparkling ◴[14 Jul 25 16:44 UTC] No.44562230[source]▶
What made you choose Litestar over fastapi (which seems to be the most popular choice right now)?
replies(2): >>44570215 #>>44571027 #
2. lutoma ◴[15 Jul 25 11:56 UTC] No.44570215[source]▶
Mostly the better documentation (last I checked FastAPI docs felt more like a series of blog posts than actual docs, but maybe that's improved). I also preferred the community-driven approach of Litestar as opposed to FastAPI's BDFL-type development structure.

I think there were also some technical details I liked better about Litestar where it was more explicit about things while FastAPI was more "opaque magic happening in the background", but to be honest I don't remember all of those.

3. robertlagrant ◴[15 Jul 25 13:36 UTC] No.44571027[source]▶
We chose Litestar over FastAPI mostly because they seemed very similar, but Litestar had a more distributed governance; i.e. a larger bus factor.

We are jealous of some FastAPI features though, so it's possible we could migrate, as Litestar's mapping between domain models, database models and API models isn't as flexible as we'd like.