Why Django?

Thoughts for the JetBrains blog post. Should write up.

```

1. Your favorite features in Django

The core request-response handlers. Request object, URL routing, and
middleware. It's the foundation of everything, and what's proven to be so well
designed through the years.

2. Productivity tips for using Django from Django insiders

Go with the grain of the framework. Use it the way it wants to be used.

If you're fighting Django, pause and ask yourself (or others) if there's a simpler way. There usually is.
Django embeds years of experience so you don't have to invent that yourself. Leverage it.

3. Use case where Django is most productive

I'm always going to go to Django because it's the familiar tool. Even if you're writing a bare-bones app, it's still quicker to use the known API rather than constantly fighting through the docs on another framework.

But Django really excels when you're building an app that needs the batteries it provides. If you need auth, or session management, or the security middlewares, or an admin, or a model layer, or any of the mature third-party apps, (and so on) then you're right in Django's sweetspot.

The point is you shouldn't be reinventing this stuff yourself. You can leverage the shared community experience, and focus on the bits that makes your app unique.

4. Anything curious you learned from Dango users

In the main, how creative you can be with a solid tool. Examples always come up
of how users have adapted Django in a way that you'd never thought of. It's remarkable, and one of the reasons we're so focused on not breaking things unnecessarily as we move forward.

5. What’s your perspective on Django in 1 year (and in more distant future)? What will be Django used for?

The next year is quite exciting. It feels like, as hopefully the pandemic continues to ease, that ideas that have been brewing slowly for the last couple of years are coming to fruition. There's already ORM changes around window expressions lining up for Django 4.2, as well as continued async improvements, and I have eyes on easier API development in core.

Exactly when these things land is hard to say, but each release I'm always humbled by the contributions that come in, and the new features that they result in.

Longer-term, Django remains a great option for solving the web problem quickly. I remember all those years ago hearing about Django, going to the website, and seeing the slogan: *The web framework for perfectionists with a deadline*. All this time later, that's still Django to a tee. I find that amazing, and exciting. It's a great place to be.

```

Start with the issue body and its five prompts, then shape the supplied notes into a coherent JetBrains blog post about Django. Done means a polished draft that addresses each prompt and is ready for review or publication; no repository file or test is identified.

Written by the indexing model from the issue text.