[moksly]

I work in a C# shop that has added Python to our development, because it runs a long side the poweshell scripts our operations guys build in the managed azure services.

I think Django is just a good package. It’s really productive and the ORM is better and easier to use than entity. The real winner for me is it’s stability though. In the time we’ve gone from classic ASP to web-forms to MVC to modern MVC to .net Core and now soon the new .Net version. Django has remained relatively stable and relatively easy to upgrade.

And make no mistake, we absolutely still operate web-forms applications that will likely never get rewritten in something else.

At the end of the day, tech stacks aren’t really that important though.

[kumarvvr]

Curiously, while Django has not changed much, Asp.net has evolved. The new endpoint routing system is very flexible. The DI system is good and templating is excellent.

Additionally, it has amalgameted into a hybrid framework, where adding a high performance API to an existing MVC app has become trivial.

Not to mention, the excellent language and support for tech like gRPC. On the whole, Asp.net core looks poised to evolve and adapt to changing tech landscape.

I do agree that the stability of Django has made it extremely easy to get an MVP off the ground, especially for a seasoned developer.

I have used both and somehow, the strong typing in C# puts enough constraints on me to reason about my web app as a proper app.

In Django and flask, I would often settle into thinking everything in terms of pieces of data, moreso because of the dynamic nature of Python.

[mixmastamyk]

If the team/project is huge typing has benefits. If not, python type hints are generally good enough. In the end using MS tooling means their needs come first and so that is to be avoided.