Live data from Hacker News

Happy 20th Birthday, Django

djangoproject.com

151–160 of 191 posts

Re: Happy 20th Birthday, Django

#151

Django is somehow the one thing in Python I never enjoyed working on. I recommend it thoroughly to people running teams since it keeps devs disciplined, but I've always been a Flask programmer at heart. To each their own. I'm glad Django exists, it's eaten plenty a share of the pie that would have otherwise gone to Rails maybe.

The couple of projects I was forced to use Flask, they both ended as a bunch of poorly assembled libraries to work like Django (admin + orm + migrations + cache) but worse. The drift from a simple Flask to monstrosity Flasknjo was so natural that I suspect it happens to a lot of people.

The ORM+migrations bit at least is pretty solid with Flask. I quite like bolting little bits on that I might need or not need.

It's like saying Django+DRF is a monstrosity compared to FastAPI/Litestar.

Re: Happy 20th Birthday, Django

#152
post #144

Happy birthday, Django. I've used, read and loved just about every part of you from the magic-removal days onwards when I had the Rails book on my desk and your docs in my browser, and you (and Python) won. I loved spending thousands of lines in a models.py modelling all sorts of problems before I touched a single line of other code. You got me into open source and then you got me into writing JavaScript seriously vi…

I'm newish to Django. Been using it for about a year. I had some experience with React earlier. But I'm more of a data engineer.

Django Cotton [1] scratched my itch fully. Very composable. Being able to pass HTML to components (E.g. you create a modal which takes a content slot) removed so many of the warts I felt using the standard Django templating.

It's not JSX, but it plays well with Django and makes it feel like I can create a real design system of components without a ton of JINJA.

https://django-cotton.com/

Re: Happy 20th Birthday, Django

#153
post #12

Earlier quoted context omitted.

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

What made you choose Litestar over fastapi (which seems to be the most popular choice right now)?

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.

Re: Happy 20th Birthday, Django

#154

20 years is an eternity in web development, and Django's longevity is a testament to its brilliant design philosophy. Happy birthday to the framework that gets things done. Django is pragmatic, secure, and unbelievably stable. It's the framework you choose when you want to build a real business, not just chase the latest trend. It has powered some of the biggest sites on the web, and it's still the best choice for a…

Wasn't Django inspired from Rails

Not really, it was a strong inter-connection between the two at the beginning, going both ways, but I'd say that Django's design philosophy was its own thing. Granted, as time goes on things have started to become fuzzier and fuzzier in my head, and not only when it comes to programming languages/web frameworks and the like.

Source: me, I was programming in Zope 20 years ago (mostly hated it, although there were lots of interesting things in at a conceptual level), switched jobs at the beginning of 2006 and thanks to the new boss I got to use Django since February of 2006 (I think I still have a 0.96 version installed somewhere on an old instance, still does its thing).

Re: Happy 20th Birthday, Django

#155

20 years is an eternity in web development, and Django's longevity is a testament to its brilliant design philosophy. Happy birthday to the framework that gets things done. Django is pragmatic, secure, and unbelievably stable. It's the framework you choose when you want to build a real business, not just chase the latest trend. It has powered some of the biggest sites on the web, and it's still the best choice for a…

Wasn't Django inspired from Rails

Not exactly. Development on what become Django began sometime in 2003, before Rails was released.

Certainly the release of Rails — and, more importantly, the questions in the Python community about what _our_ web dev story would be — inspired us to extract the framework from the rest of our code and release it. And over the years we’ve taken some inspiration from Rails (as well as anywhere else we see good ideas). The biggest one probably being the basic ethos that web development should be easy — the focus on what we now call “Developer Experience” is the best thing Rails gave the world, I think.

Re: Happy 20th Birthday, Django

#156
For something to endure so long in the web dev world is a real testament to all the people in the community that do the mundane 'gardening' work each day. Pruning back 'dead' parts of the framework and smoothing out rough edges as the world evolves.

Re: Happy 20th Birthday, Django

#157

Earlier quoted context omitted.

Wasn't Django inspired from Rails

Not really, it was a strong inter-connection between the two at the beginning, going both ways, but I'd say that Django's design philosophy was its own thing. Granted, as time goes on things have started to become fuzzier and fuzzier in my head, and not only when it comes to programming languages/web frameworks and the like. Source: me, I was programming in Zope 20 years ago (mostly hated it, although there were lots…

Zope, shudder. It had some amazing ideas and I built a reasonably large app on it, but I’d rather swallow my own tongue than work inside an application server again.

Django and its contemporaries, like TurboGears and Pylons, were a breath of fresh air.

Re: Happy 20th Birthday, Django

#158
post #94
post #85

Earlier quoted context omitted.

I don't think Django could have talked to sqlite over the network, or would have really solved any problems. When I say physically separate, I mean it in the pre-cloud sense: one front end server (Django) dynamically connecting to a database on a remote server (based on the user account), which had a database continuously logging streams of sensor data from local IoT devices. What I did was change the architecture to…

Django has supported database routing for ages. I've abused it for setups like yours (at least as I vaguely understand from the post details) to avoid using a datalake

It was added over a year after we needed it (back in 2008/2009). I'm pretty sure our use case was taken as an input into the design of Django's database routing. We were certainly loud enough about it.

Re: Happy 20th Birthday, Django

#159
I owe my career to Django, I used it to build some projects when I first started my career, and recently reached for it when I was asked to build another huge project. The built in admin panel is the killer feature.
Post reply on HN