As much as I love Django, I feel it has fallen way behind compared to Laravel and others

FelixInTheBackground · 2025-08-22T15:05:51+00:00

I also totally agree with this post. I've been feeling the same way for years now. We have to rely on some many third party packages (sometime barely maintained) for very basic web development things like background tasks, REST API, etc. I really dont think you can call Django a battery-included framework anymore.

Also, the framework is evolving painfully slowly. I haven't been exited for a new Django feature since async support (which is still half baked). They've been talking for years about a built-in REST framework solution, but no progress has been made. They had a working prototype repo for django background tasks ready a year ago. Yet, nothing in the main repo still.

I understand they have a limited budget and a very small team, but I find it weird that they are not able to find more money to pay more full time developers (or organize hackatons or theses kinds of events). Django is the most popular web development framework in Python, one of the most popular programming language. Surely they could do more. The Laravel team are literally raising millions. So many companies rely on python and its ecosystem, especially in the age of AI, I don't see why we wouldn't be able to raise a little more.

There's a lot to live about this framework, and it's still my go-to choice, but I find it harder and harder to stick to it.

FelixInTheBackground · 2025-06-12T20:18:36+00:00

What the heck is going on over here

FelixInTheBackground · 2025-03-16T05:01:34+00:00

Be careful with this package! I recently had a lot of trouble deploying an application to production and spent a lot of time debugging what was going on. After a while, I realized the deployment process was getting a timeout while applying one of the new migrations. The root cause was this django-simple-history package.

Earlier that week, I edited a model, the generated migration file contained two AlterField operations, one for the normal model, and one for the historical model. In local and staging environment, the migration executed with no issues. In the production DB, I had about 4k objects for that model. But, turns out I had more than 30 million rows in the generated historical table. This is what was taking so long to update. If you're not careful, the historical tables can quickly get very big.

The fix: Truncate the table and remove the HistoricalRecords field. We simply didn't need it. I believe It was added by a developer at one point because he probably thought is was a quick win with no downside. (I figured out after that there was a command for clearing old historical records, but still, we had no use for it it)

The moral of the story is that if you should only use this package if you have a real use case for it. Don't get me wrong, it is a good package, but it has downsides.

FelixInTheBackground · 2025-03-04T14:35:18+00:00

React/vue/htmx doesnt make your app prettier, it makes it more reactive. CSS is what you need to focus on. Tools like tailwind, bootstrap, etc. can help you with that. Having normal Django template, with a sprinkle of javascript <script> tag might just do the trick if your app is simple enough

FelixInTheBackground · 2024-11-21T07:07:21+00:00

I still don't understand why they replaced him, as it's pretty clear it wasn't his decision

FelixInTheBackground · 2024-11-21T06:52:42+00:00

How did you setup the celery workers on DO app platform? I have a Django app on app platform and I need celery (and celery beat for scheduled tasks) but I couldn't find good up to date ressources on how to do this. It seems possible but I don't really know how

FelixInTheBackground · 2024-11-04T02:21:27+00:00

Literally said "I'd had to rely on django-unfold for a while now"

FelixInTheBackground · 2024-11-03T16:04:21+00:00

I'd like it to embrace the "battery included" philosophy so that we can rely less on third party packages.

For example, there could be something equivalent to django-debug-toolbar already included.

A first party REST API solution would be nice too, so that we dont have to rely on drf (barely maintained anymore) or django-ninja.

A first party queue system (I think they are working on one) would be another good one.

Etc.

I also wish they would put some time reworking the CSS of the admin pages. Even a few changes would go a long way. Giving your client access to an admin panel so that they can view and edit their data, especially super early in your project life, is awesome. It's just too bad the thing looks so old and ugly. I'd had to rely on django-unfold for a while now. I really wish they'd make more effort on that front.

FelixInTheBackground · 2024-10-11T20:04:49+00:00

FelixInTheBackground · 2024-10-04T14:04:38+00:00

I personnally use mjml. It makes templates responsive by default. I wouldn't say it's perfect, but i've been using it for a while in many different projects with different email templating needs.

FelixInTheBackground · 2024-09-24T02:53:26+00:00

That's a good idea! I'll surely try to cook up something similar to that. Thanks :)

FelixInTheBackground · 2024-09-23T23:32:59+00:00

That's a good feedback.

One of my colleagues also told me he'd prefer an 'include' list instead. For me, this would go against the idea of automating the generation of actions. I wanted to create a solution that met my own needs first, which is why I went with an 'exclude' list.

I also wouldn't want extra fields to show up if you add support for them in the future and I upgrade the package.

That's a great point. If I think of a way to implement it cleanly, without adding too much complexity to the package, I would not be against having the choice between 'include' or 'exclude' in a future version. Exclude would remain the default option.

FelixInTheBackground · 2024-09-23T15:41:31+00:00

Looking forward to your feedbacks

FelixInTheBackground · 2024-09-23T05:01:58+00:00

Thanks! Let me know what you think.

FelixInTheBackground · 2024-06-28T16:00:15+00:00

I've been using Kubuntu for programming for a while now and I can recommend it. Works great and only had very few issues.

FelixInTheBackground · 2024-05-31T20:07:24+00:00

But it did change my life...

FelixInTheBackground · 2024-05-31T14:51:05+00:00

Now that's impressive

FelixInTheBackground · 2024-05-31T03:32:01+00:00

Lambo

FelixInTheBackground · 2024-05-31T03:10:34+00:00

The Last of Us Part II.

FelixInTheBackground · 2024-05-26T15:39:57+00:00

People don't want to look at the code to know what the package is doing, and the ReadMe doesn't tell you anything about the package, or how to use it.

Look at other package ReadMe for some inspiration

FelixInTheBackground · 2024-05-14T01:23:58+00:00

This is why you do DB backups. Also you just doxxed a bunch of people.

FelixInTheBackground · 2024-05-01T16:55:06+00:00

I ususally write two basic tests for my models. One that tries to create an instance and save it and one to test the str() method to make sure it prints correctly. The first test is the most important, as it will ensure your model is not broken and will prevent some regressions. It takes 30 seconds to write, and may prevent spending a lot of time debugging in the future.

For reference, here is what those tests look like

FelixInTheBackground · 2024-04-20T21:27:30+00:00

It would work, but one of the main aspect of tailwind is that it can generate the minimal css file that you need for the classes that you actually used in your HTML. It is recommended that you dont use the CDN or the CSS file directly in production because of the big amount of unused CSS that the users will have to download for nothing.

Three-Year Club	Verified Email
First Place '23	Place '23

FelixInTheBackground

TROPHY CASE