Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 5.0

djangoproject.com

Post reply on HN
Print view View original

81–90 of 237 posts

Re: Django 5.0

#81

Post by megaman821 »

miiiiiike wrote: post #75
megaman821 wrote: post #72

Earlier quoted context omitted.

Django Ninja just hit 1.0 a few weeks ago. I think you are going to have to be patient to find large sites using it in production.

I've never heard of anyone using it in production, period. The one thing FastAPI had going for it back when it was announced was a list of companies and groups with it deployed that minute. Is it a "1.0 because we think it's done and you should try using it now. Maybe it'll work." Or "This is a solid 1.0 that has been tested in production. You can expect reasonable api stability." FastAPI launched with option three:…

I am using it myself on a branch I haven't pushed to production. I would say DRF has better documentation and more packages that extend its behavior (like exporting to Excel). Ninja is a lot cleaner though, it works better with type checkers, and if you are also using FastAPI there is basically no learning curve.

Re: Django 5.0

#82

Post by cdcarter »

jmduke wrote: post #22

My app is a Django backend and a Vue frontend. There are large swathes of Django that I ignore, but to me the core of Django — its ORM, routing and middleware system, and admin interface — are worth their weight in gold. The migration from DRF to Django-Ninja (which is, roughly, FastAPI + Django) has also been a great improvement in terms of productivity and performance. Not a lot of whizbang features in 5.0, but Gen…

GeneratedField looks interesting, but I'm not _really_ sure what gains I get over just calling annotate() on my queryset with some computed fields. At least on the backends where the computed GeneratedField isn't stored.

Re: Django 5.0

#83

Post by collyw »

saasjosh wrote: post #7

Another boring release without much innovation. I wonder what's stopping Django from releasing more useful features like other frameworks are doing. Maybe the team is stuck in the past. They've been trying to improve forms for a long time but it still sucks. I think they should just remove it at this point and let external packages solve the problem.

> Another boring release without much innovation

That's a good thing. A couple of articles related to the topic.

https://boringtechnology.club/

https://www.david-dahan.com/blog/10-reasons-mvc-frameworks-a...

Re: Django 5.0

#84

Post by megaman821 »

rigoleto wrote: post #65
ralmidani wrote: post #35

Django made me fall in love with programming 13 years ago, and since then it has always had a special place in my heart. I’m revisiting a business idea I was working on for a couple years, before I sought and found employment in the industry (where I used Java for a couple years, then Elixir for a couple more). My project was built with Django and Django REST Framework, and Ember on the client-side. 6 years later, th…

> I’m going to skip the drama and just use htmx for the client-side. Render Django templates server-side, include a single JS script, thrown in some HTML attributes, distinguish between full page requests vs. requests for a partial with updated data, and call it a day. More of a side comment, but I'm skeptical of the way HTMX encourages partial renders like this. It feels like a premature optimization that adds more…

There is a package, https://github.com/carltongibson/django-template-partials, that is basically like server-side hx-select, when there is some performance concern. Overall, I agree with you though, hx-select is going to be fine most the time.

Re: Django 5.0

#85

Post by nrjames »

miiiiiike wrote: post #75
megaman821 wrote: post #72

Earlier quoted context omitted.

Django Ninja just hit 1.0 a few weeks ago. I think you are going to have to be patient to find large sites using it in production.

I've never heard of anyone using it in production, period. The one thing FastAPI had going for it back when it was announced was a list of companies and groups with it deployed that minute. Is it a "1.0 because we think it's done and you should try using it now. Maybe it'll work." Or "This is a solid 1.0 that has been tested in production. You can expect reasonable api stability." FastAPI launched with option three:…

Not a large site, but I used django-ninja in production for internal tooling at a very large game dev/publishing company. The APIs routinely handle 1000s of calls (via an integration with Dagster) for moving large amounts of data around and into a reporting system. It's rock solid and fast. I'm on v0.22 however and need to do some refactoring to move to 1.0 because of changes to the integration with Pydantic.

It is so easy to set up and use and it's at worth giving it a spin if you're curious.

Re: Django 5.0

#86

Post by biscotti »

yunohn wrote: post #50
dexwiz wrote: post #42

Earlier quoted context omitted.

Isn't Developer DX mostly a way to get developers locked into your platform? I have avoided Next.js for this reason, it seems like just a way to funnel developers towards Vercel. DX is largely a service specific problem since its coupled to the service you are deploying to.

Django is free, in all definitions and purposes of the word. No agenda, no VC funding, no BS.

[dead]

Re: Django 5.0

#87

Post by miiiiiike »

megaman821 wrote: post #81
miiiiiike wrote: post #75

Earlier quoted context omitted.

I've never heard of anyone using it in production, period. The one thing FastAPI had going for it back when it was announced was a list of companies and groups with it deployed that minute. Is it a "1.0 because we think it's done and you should try using it now. Maybe it'll work." Or "This is a solid 1.0 that has been tested in production. You can expect reasonable api stability." FastAPI launched with option three:…

I am using it myself on a branch I haven't pushed to production. I would say DRF has better documentation and more packages that extend its behavior (like exporting to Excel). Ninja is a lot cleaner though, it works better with type checkers, and if you are also using FastAPI there is basically no learning curve.

Django Ninja has always looked beautiful. I've been toying with it since it was first announced, never pushed it to production tho. I've been thinking of spinning up a cluster just to dark launch it with calls from my main app to see how it performs.

Re: Django 5.0

#88

Post by miiiiiike »

nrjames wrote: post #85
miiiiiike wrote: post #75

Earlier quoted context omitted.

I've never heard of anyone using it in production, period. The one thing FastAPI had going for it back when it was announced was a list of companies and groups with it deployed that minute. Is it a "1.0 because we think it's done and you should try using it now. Maybe it'll work." Or "This is a solid 1.0 that has been tested in production. You can expect reasonable api stability." FastAPI launched with option three:…

Not a large site, but I used django-ninja in production for internal tooling at a very large game dev/publishing company. The APIs routinely handle 1000s of calls (via an integration with Dagster) for moving large amounts of data around and into a reporting system. It's rock solid and fast. I'm on v0.22 however and need to do some refactoring to move to 1.0 because of changes to the integration with Pydantic. It is s…

Thanks. 1,000s of calls a second/minute/day?

Re: Django 5.0

#89

Post by pphysch »

bdzr wrote: post #56
pphysch wrote: post #49

Earlier quoted context omitted.

I would point to two of the most popular plugins, Django Rest Framework (DRF) and Celery (a background task system that requires rabbitmq|kafka|redis|etc). Both add highly sought-after features, but I believe these implementations are quite poor, complicated. Django could implement MVPs in core/contrib and vastly simplify future projects for users. A builtin OIDC client abstraction would go a long way as well.

The worst thing about DRF is the dogmatic adherence to inexplicable class hierarchies, something that is modeled after Django class based views. I think Django would fumble a DRF implementation.

All you really need is a decent built-in JSON de/serializer for Django models. It doesn't need to be an OOP monstrosity.

Golang has that built-in to what is a simpler language than Python (e.g. no class inheritance).

The complexity of DRF greatly oversteps what it is offering.

Re: Django 5.0

#90

Post by dopamean »

asylteltine wrote: post #54

I like Django rest framework a lot. It was really easy to make something with react and call Django directly however the templating engine is also great. It’s so strange people still use rails

You should learn a bit about Rails. It wont be strange that people still use it.
Post reply on HN