The Decline of Django

Either is good if what you are building is something small and very focused or if you already know exactly what you want to build and want to have freedom making decisions about most aspects of the application.

But if you don't know yet what the product will be, a battery included framework like Django is very nice to get out the door quickly without having to worry too much how to structure the code, what library to use for x, etc.

Something like FastAPI would be better suited to a narrow use case like that, as that's what it specializes in.

The async issue is valid — I have wanted to use server-sent events with intercooler/htmx — but the answer seems to be just to use Django Channels, or be patient and wait until the async features are actually finished.

Django, many years later, still presents a straightforward solution to a straightforward problem, (almost) all batteries included.

2) Onboarding new developers lacks IDE specific tooling for free

3) Admin GUI isn't great

4) Async support is still incomplete

5) Static types aren't used in Django

6) Django is MVC which isn't useful if you just need a light V

7) People ignore other, newer tech because Django exists

What??? 4 and 5 are legit complaints, the rest is literally the nittiest of picks, in my opinion. You don't like a framework because it's so good, people don't experiment with newer frameworks?? And that's in your article about the decline of that framework?

This is a weird article, man. I am surprised they haven't figured out async yet, and I guess if you really like static types the lack of them in Django would be annoying, but otherwise this just seems like you set a goal to write about a topic, and forced yourself to come up with an article you thought hasn't been written before. Like, it feels like you wrote the title of the article, and then tried to come up with the rest of it after the fact.