News for hackers. Stuff that matters.
Re:Django 2.2 by trpc on Monday April 01, 2019 @12:16PM (#19544918)
Whenever I see people still praising Django in 2019, I immediately know that their technical understanding of the current backend and ops technologies is years behind. Django is still okay for small and amateur projects but nothing more than that. It is a curse for a fast moving business.

EDIT: even though I stopped writing Django for 3 years now but here are some of my reasons as far as I can remember:

1. mediocre routing (no nesting, all routes have to be declared in one place)

2. mediocre middleware (middleware is global)

3. mediocre ORM (easy only for very easy stuff, more pain in the ass than writing raw SQL itself when it comes to complex aggregations and joins) not to mention some of the famous ORM bugs that have been open for like a decade

4. custom user model? good luck fighting with Django errors to make that happen

5. custom authentication? external authentication? good luck

6. Django is built for 2000s websites not REST/gRPC era

7. want to use graph databases? noSQL? good luck

8. external migration for SQL? oh god, prepare yourself for the mental hell

9. Django as far as I can tell still ONLY supports decoding "x-www-form-urlencoded" bodies, yeah no JSON, it's that pathetic

Django is very intrusive and is pain in the ass in a fast moving environment where you want to use microservices, external authentication/authorization, APIs, gRPC, etc... that's excluding all problems of Python itself. I totally recommend Typescript/Express or Golang for doing any kind of non trivial backend with fast moving environment/requirements currently

Re:Django 2.2 by acdha on Monday April 01, 2019 @01:42PM (#19545921)
No need to troll if you don't like it — move along and don't waste everyone else's time waving your ignorance around so proudly.
[dead]
Re:Django 2.2 by acdha on Monday April 01, 2019 @02:28PM (#19546498)
Feel free to substantiate your claims. Even after your edit it's just a bunch of big claims with no supporting evidence for the things which aren't simply wrong (e.g. “no nesting, all routes have to be declared in one place” sounds like you haven't ever used a Django app, including the built-in ones. Perhaps there's something else you have in mind but since you didn't explain, who else can tell?).

Lobbing insults won't hide the fact that you aren't even trying to make a technical argument or otherwise contribute in any way to the discussion:

> Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents.

> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.

https://news.ycombinator.com/newsguidelines.html

[dead]
Re:Django 2.2 by dang on Monday April 01, 2019 @02:39PM (#19546613)
Could you please stop? Flamewars are just what we're trying to avoid on HN. When accounts behave like this we eventually have to ban them.

https://news.ycombinator.com/newsguidelines.html

Re:Django 2.2 by trpc on Monday April 01, 2019 @02:43PM (#19546651)
I am not trying to start any flamewar, I am just stating why Django is not good imo, simple as that
Re:Django 2.2 by dang on Monday April 01, 2019 @03:08PM (#19546967)
I believe that you started out that way. The problem with that first comment was that you began with an insult ("I immediately know that their technical understanding of the current backend and ops technologies is years behind"), which provokes people rather than informing them. Also, your comment included name-calling, which the site guidelines ask you not to do. Could you please review https://news.ycombinator.com/newsguidelines.html and follow the rules when posting here?

After that, you followed up with personal attacks and incivility. That's definitely flamewar. You weren't the only one doing it, but that doesn't make it ok.

[deleted]
Re:Django 2.2 by dang on Monday April 01, 2019 @02:41PM (#19546628)
Please stop also. Flamewar is not what we want here, and https://news.ycombinator.com/item?id=19545921 was as much a violation of the site guidelines as the comments you're criticizing.

If someone is wrong, provide correct information and move on. If a comment breaks the guidelines, flag it and move on. In egregious cases, you're welcome to email us at [email protected]. But please don't respond in kind or perpetuate spats.

Re:Django 2.2 by acdha on Monday April 01, 2019 @03:34PM (#19547236)
Sorry about that — I deleted my last comment before your reply for the same rationale rather than wasting more time on a thread started in bad faith.
Re:Django 2.2 by zimablue on Monday April 01, 2019 @12:36PM (#19545147)
This post is very antagonistic but I can say that point 3 rings very true, even using advanced/data heavy SQL got very annoying for me relative to SQLAlchemy and I don't think you really want to try and pull it out.
Re:Django 2.2 by preommr on Monday April 01, 2019 @07:02PM (#19549261)
It's been a while since I've used SqlAlechmy, but I remember absolutely hating it. Like you said, Django's ORM fails above very simple manipulation and even though SqlAlchemy might be better, it was still awful. I found it better to just write raw sql for my few use cases than to dive into page after page of sqlalchemy documentation.
Re:Django 2.2 by dcbadacd on Monday April 01, 2019 @12:48PM (#19545289)
I second to this, SQLAlchemy was nicer to use when my data model wasn't super simple and used PostgreSQL specific features.
Re:Django 2.2 by spectaclepiece on Monday April 01, 2019 @12:19PM (#19544948)
Would you mind sharing some more precise reasoning with regards to this statement?
Re:Django 2.2 by skullborg on Monday April 01, 2019 @12:23PM (#19544990)
Don’t bother, the poster doesn’t follow up his/her posts with any information backing up their statements or claims.
Re:Django 2.2 by joelbluminator on Monday April 01, 2019 @12:23PM (#19544989)
As opposed to?
Re:Django 2.2 by drinfinity on Monday April 01, 2019 @02:36PM (#19546572)
You guys hate, but he is right and you know it. In year heart you feel this call, this.. twinge. You know this is not the True Path.

I've done it both. Our Go + Angular project slaughtered Django and now I was dealing with services running at 25MB RAM with single digit CPU usages instead of the disgusting gluttons that Python and Ruby produces with memory usage measured in GBs. Production servers can have specs rivalling Raspberry PIs instead of IBM Blue Genes. Quite refreshing.

The illusion of power that Django (and all fat frameworks) create works OK if you work with a narrow set of very specific web applications in a static environment with a team of Django specialists. Anything else and the project turns to shit.