Are people still using Django?
Portable Django
11–20 of 71 posts
Re: Portable Django
#12Why?
[dead]
Re: Portable Django
#13Are people still using Django?
Are people still using a mature, stable, battle-tested framework with tons of third-party resources, great documentation and excellent coverage of many business needs ?
Yes, of course.
Re: Portable Django
#14Are people still using Django?
I've seen this opinion on HN for years, but still don't _really_ understand it. Our cofounder built what is now a $1B+ SaSS company from some cursory SQL knowledge he gained while interning at a hospital in the early 2010's. The entire business is, in essence, a fancy graphical UI around postgres.
I've now been writing django at work for five years and still have yet to come across a query builder/orm which is as powerful yet simple in addition to being a breeze to on-board new engineers with.
When there are queries that require the use of non-django builtins, it's also relatively easy to use django raw sql or just straight up use the psycopg2 sql.SQL dynamic string composition helpers.
With the complexity of some our chained django QueryMethods, the company would have quite literally been impossible to build without django's query builder, at the very least.
Re: Portable Django
#15Earlier quoted context omitted.
djngo.com is the culmination of years of effort, creating a single file python executable that runs on all platforms. This project is based on APE ( https://justine.lol/ape.html ) and in the past few days, our Python APE port (called python.com) became good enough to run Django. So we put Django inside the executable too, and called it djngo.com. The djngo.com executable will just work on the following platforms: - A…
Why Django 2.2? That version is no longer supported, and I'm guessing there's some technical reason you are using the obsolete version? (Production Django is now on major version 4)
The cosmo monorepo currently vendors Python 3.6, since cosmo originally didn't have threads support and that was the last version before threads became mandatory. I'm pretty happy with the old version since I've been using Django since the 2000's. I put a lot of work into enhancing monorepo cosmo python with things like a better REPL that works across platforms. It may not be supported by the Python team, but it's supported by me. However the future will probably be building Python w/ Cosmo outside the monorepo. See the other comments for details on how to use APE + Python 3.11 for a modern experience.
Re: Portable Django
#16Are people still using Django?
After a few years around the block (meteor, next.js), I'm back to Django. Got an mvp planetary web map annotation app up in no time, using Django DRF and just some plain hand-written js. Feels great to be back.
Re: Portable Django
#17[deleted]
Re: Portable Django
#18Why?
Perhaps it could be an effort toward an implementation of Local-First Web Development. [1]
Re: Portable Django
#19Are people still using Django?
Not to be condescending or patronizing, but, well, I'm answering your question and it itself has a dismissive tone.
Yes, people are still using Django.
As I've grown in my career, frameworks, libraries, and architectural patterns just become tools. I don't quite understand folks who identify as a "React developer", or a "Django developer". When evaluating any framework, you must learn to eschew the latest hotness long enough to evaluate what your requirements are, and maybe most importantly, what your constraints are.
For a surprising amount of projects today, I would still recommend Django above anything else.
Re: Portable Django
#20Are people still using Django?
I've seen this opinion on HN for years, but still don't _really_ understand it. Our cofounder built what is now a $1B+ SaSS company from some cursory SQL knowledge he gained while interning at a hospital in the early 2010's. The entire business is, in essence, a fancy graphical UI around postgres. I've now been writing django at work for five years and still have yet to come across a query builder/orm which is as pow…
This is a double-edged sword in my opinion. The Django ORM is among my favourite ORMs, but the abstraction (like any) can cause problems over time.
At scale, poorly understood ORM-generated queries can be a real pain, especially if your team's SQL skills have atrophied due to over-reliance on the ORM.
As an exercise, I'd possibly recommend reviewing your top 1-3 worst performing queries, tracking them back to the ORM, and evaluating how to improve them.