New Features in Django 3.2(hakibenita.com)
hakibenita.com
New Features in Django 3.2
https://hakibenita.com/django-32-exciting-features
4 comments
Finally some support for building JSON Objects in Django! Can't wait to test it out soon.
Django 3.2 has only been released as a beta 1. Title is a bit click-baity and feature set can still evolve.
That’s not really correct: beta marks feature freeze for the release. So there will be bug fixes before 3.2 final lands, but no new features.
I stand corrected. So what happen if a major bug is found late in the process ? I suppose either the feature is dropped for this release or the release delayed until the bug is fixed and the feature is kept. Do you know which is it ?
There isn't a hard policy; it'd be a case-by-case decision. If there wasn't rough consensus, it'd be up to the release manager and technical board to decide. So far, this hasn't really happened: there have been a few bugs that have delayed releases by, like, a few days or a week, but nothing so severe that has seemed to warrant pulling a feature down.
I used to be such a huge Django fan, and in many ways I still am.
I've built more than one business around it.
For the past six or seven years though, I've found Nodejs to just be superior in every aspect other than the automatic admin.
Strapi has some interesting options there though.
I've built more than one business around it.
For the past six or seven years though, I've found Nodejs to just be superior in every aspect other than the automatic admin.
Strapi has some interesting options there though.
The power of Django (imho) is in how you can define data models only once, and out of them get excellent database migrations, database operations, form validation, API serialization/deserialization, and an admin interface. Is there anything in Node.js land that comes even close to this level of integration?
Last time I worked on a Node app, I had to define the data model once for the ORM (Objection), again when writing migrations by hand (Knex), again when defining the input validation schema (Joi), maybe again when defining data objects, and I didn't even have an admin.
For me, the language is secondary -- there were times when I would have liked to have a Django.js, so I could share code (validation and calculation modules) between backend and frontend.
Last time I worked on a Node app, I had to define the data model once for the ORM (Objection), again when writing migrations by hand (Knex), again when defining the input validation schema (Joi), maybe again when defining data objects, and I didn't even have an admin.
For me, the language is secondary -- there were times when I would have liked to have a Django.js, so I could share code (validation and calculation modules) between backend and frontend.
I use mongoose and mongodb mostly with node, because the technologies marry so well. I generally ETL over to pg for heavy analytics workloads.
This is such a great comment, thanks.
I agree.
I've switched over to the Jamstack, and life is much easier.
If I need something fast and easy, I use the AWS amplify pretty heavily, and their new admin UI has been very useful for me.
Ref - https://aws.amazon.com/about-aws/whats-new/2020/12/aws-ampli...
Ref - https://aws.amazon.com/about-aws/whats-new/2020/12/aws-ampli...
Every aspect? The underlying language must be another one no? Python isn't perfect, but it's a lot more pleasant to work with than Javascript
Maybe 5 years ago. I code python for living, and I've found modern javascript to be pretty pleasant these days, and imo I prefer async in javascript than python.
It's nice to see Django being awesome and actively developed, but it feels like Django is losing touch.
The world has moved on to concurrency and Django, as a framework, seems ill-suited to meet future requirements.