What I love about Django
91–100 of 120 posts
Re: What I love about Django
#92Re: What I love about Django
#93Earlier quoted context omitted.
I don't hate the guy (I don't know him personally so I cannot hate him), I just disagree with his opinions and I personally don't want to use anything that he makes or endorses. Easy as that. I know that there are other people contributing to Rails, and that's their choice. Other people stopped contributing once DHH showed his true nature.
I presume, that you're not shopping anything on shopify?
Re: What I love about Django
#94Earlier quoted context omitted.
It's not hate, it's not wanted to be associated with: see https://victorwynne.com/dhh/
I read the original post DHH links to. I don’t think it warrants the kind of hate he gets. DHH has always been very outspoken in his opinions. That’s why he bashed Heroku so badly when he introduced Kamal. It’s what makes Rails such a clear minded framework. In his political blog, he’s raising an issue that’s occupying all of western politics. And he’s very aggressive about it - just how he was very aggressive when h…
What a weird statement. He has a platform, people that think his content is hateful and racist don't have a platform. He writes about kicking out normal people living their lives from places that he is not even from. Antagonizing people in position of power with this kind of mentality is what every sane person should do.
Re: What I love about Django
#95The only part I don't really agree with, is the avoidance of app separation and signals. It's one of the cleanest ways to decouple your modules and keep some level of sanity in a medium-sized codebase. It comes down to deciding what parts really need to depend on others and be very explicit about that. I generally end up with a few core apps with the main data objects that a lot of other "parallel" ones depend on, a…
I always wonder about signals. I found them incredibly attractive from a code cleanliness standpoint, but every team I’ve joined avoided them either because they got burnt by them or because of superstition from blog posts by people who got burnt by them. It may be a cognitive load thing, that in smaller codebases it’s easy enough to remember “these three things fire a signal when saved”, but bites you in the ass whe…
I do what I must in the atomic context, and trigger celery tasks for everything else.
Re: What I love about Django
#96Django makes simple things easy and complex things hard. Django breaks the zen of Python with much "magic". I like DjangoORM but prefer FastAPI for the webby bits.
[0]: https://litestar.dev
Re: What I love about Django
#97Most loved feature, for me: No dramatic changes, just sane and careful evolution.
This is so important. I've been using Django for around 20 years and my current code base is 10 years old. Not having to do major rewrites or stick on outdated versions really matters.
Re: What I love about Django
#98Earlier quoted context omitted.
It's not hate, it's not wanted to be associated with: see https://victorwynne.com/dhh/
I read the original post DHH links to. I don’t think it warrants the kind of hate he gets. DHH has always been very outspoken in his opinions. That’s why he bashed Heroku so badly when he introduced Kamal. It’s what makes Rails such a clear minded framework. In his political blog, he’s raising an issue that’s occupying all of western politics. And he’s very aggressive about it - just how he was very aggressive when h…
Re: What I love about Django
#99Earlier quoted context omitted.
It's made by DHH.
The DHH hate is absolutely crazy on HN. I don't understand how people can be so out of touch.
He is probably at a KKK level of racism.
Re: What I love about Django
#100Django while opinionated is very flexible too. unlike Rails. that means you can mold it to fit your use case easily - don't like the ORM - you can plug SQLalchemy and use a different 'architecture'. + you can use multiple different databases if you think that's the right path. in Django there's no 'the rails way' - you choose your own path. Django-admin by itself saves so much work specially If you're doing B2B stuff…
whereas Django though it also provides almost similar abstractions in terms of CRUD - it doesn't assume your app will only do CRUD stuff - hence the flexibility e.g there's many apps where you only have a handful of endpoints that are user accessible maybe at most 15, then of course management of users via Django-admin but everything else is non CRUD e.g calling other systems
[0]: https://jeromedalbert.com/how-dhh-organizes-his-rails-contro...