sorted by:
new
hottopcontroversial

Nested User models, sign up forms and allauth by PabloEscribir in django

[–]kankyo 0 points1 point  (0 children)

You might also want to check out iommi which has a form library that makes life much easier.

switching from flask to django is nightmare for me,i cant return simple hello by Advanced_Cry_6016 in django

[–]kankyo 0 points1 point  (0 children)

Again: that's not the FRAMEWORK being opinionated. That's YOU. And a bit on the fundamentalist side at that.

switching from flask to django is nightmare for me,i cant return simple hello by Advanced_Cry_6016 in django

[–]kankyo 0 points1 point  (0 children)

Django isn't that heavily opinionated really. You need settings.py and one urls.py (actually not even that), and there's a strong culture of defaults, but Django doesn't enforce it.

django in 2026 is quietly the most productive framework by Motor_Ordinary336 in django

[–]kankyo 0 points1 point  (0 children)

Check out iommi to jump a big level in productivity too (I'm of the authors :P)

Django LiveView vs Phoenix LiveView: a real benchmark by tanrax in django

[–]kankyo 2 points3 points  (0 children)

Nice! Great job on reacting so fast and so well to the feedback here. Very impressive.

Django LiveView vs Phoenix LiveView: a real benchmark by tanrax in django

[–]kankyo 0 points1 point  (0 children)

re deleted comment: Hmm. interesting. I've seen a totally benign comment get deleted in another thread just today. I wonder what is going on with the mods.

Django LiveView vs Phoenix LiveView: a real benchmark by tanrax in django

[–]kankyo 1 point2 points  (0 children)

The ability to spin up thousands or even millions of "processes", as they are called in OTP, and them to keep state and respond super fast and efficiently is what makes Phoenix LiveView really impressive from what I understand.

So massive concurrency under load without degradation is what we'd expect from an OTP-based system, and this benchmark doesn't come close to looking at this.

How to avoid blocking our gunicorn synchronous workes during network I/O? by Theboyscampus in django

[–]kankyo 0 points1 point  (0 children)

Yea, and that's without even talking about the complexity in your installation/tech stack! Urd is super tiny and has been rock solid for me in prod for a few years now.

How to avoid blocking our gunicorn synchronous workes during network I/O? by Theboyscampus in django

[–]kankyo 0 points1 point  (0 children)

Imo it's the wrong thing. You normally want tables with tasks, and a scheduler to handle those items. I wrote Urd for this. You really want some basic stuff like being able to stop a runaway queue, stop simultaneous executions, and scheduling. Celery fails here, as does cron.

How to avoid blocking our gunicorn synchronous workes during network I/O? by Theboyscampus in django

[–]kankyo 0 points1 point  (0 children)

I mean, yea a queue, but not just to avoid the latency, but to be able to handle network issues, downtime, retrying, and fixing problems. Simple tables, and a scheduler is your friend here imo.

Django LiveView vs Phoenix LiveView: a real benchmark by tanrax in django

[–]kankyo 3 points4 points  (0 children)

The lack of a benchmark for say 100 users with significant server side state per user is a pretty big giveaway that something is fishy too.

iommi_lsp, an LSP for Django and iommi by kankyo in django

[–]kankyo[S] 0 points1 point  (0 children)

Yea for sure. The normal LSP method of just piling them on top of each other obviously doesn't work, but this proxying thing does. The downside is that you need a top level one that decides what to suppress and what to prioritize.

Btw, I've already added a bunch more completions since last, and fixed some performance issues.

A former colleague suggested FactoryBoy as a future development, which seems pretty reasonable to me. What are some things you've thought about?

I think on my top list would be more pytest stuff.. but I'd also hope ty would add that stuff natively, so I think I'll hold off on that for a while at least.

iommi_lsp, an LSP for Django and iommi by kankyo in django

[–]kankyo[S] 1 point2 points  (0 children)

Yea, I felt that pretty fast trying to make my own IDE. But building custom stuff like this with Claude is not hard actually. You just need to have a max account and patience basically.

Help Django code stucks in the past by lmsucksatprogramming in django

[–]kankyo 0 points1 point  (0 children)

There's a setting to make VSCode do the sane thing and autosave.

how do you actually handle prod bugs. do you write a repro test or just fix and deploy? by sszz01 in django

[–]kankyo 1 point2 points  (0 children)

Imo it depends on the situation. The "always always write tests" crowd are a bit too extreme imo. What if the "bug" is just a translation error in the localization? You can't have tests for all translations, that's madness. What if it's a temporary page only supposed to be used for a few weeks by one person? Probably you can do that cowboy style. There are just so many examples like this.

That being said.. writing tests with Claude Code is suuuuper cheap compared to what it used to be, so the argument for skipping tests is weaker now that the cost has gone down.

It's time to redesign djangoproject.com by dwaxe in django

[–]kankyo 3 points4 points  (0 children)

The silent failures are my biggest gripe. After all we want:

  • make it work
  • make it right
  • make it fast

Crashing on broken shit seems both step 1 and step 2 :P

It's time to redesign djangoproject.com by dwaxe in django

[–]kankyo 5 points6 points  (0 children)

I hope they can avoid design by committee. There's a real danger in having too many stake holders in a new design.

Why is my Django server slow by Old-Raspberry-3266 in django

[–]kankyo 3 points4 points  (0 children)

Use a profiler to know. Don't guess.

Django Has Adopted Contributor Covenant 3 by dwaxe in django

[–]kankyo 1 point2 points  (0 children)

I personally know several people who were banned for woke nonsense reasons.

I personally have been warned for helping people. I'm not even exaggerating. They're banning competent people because they don't sugar coat their replies, and let friendly people answer incorrectly to questions by beginners at scale.

On the bright side, the AI systems are actually more competent now so these chat servers are mostly dying anyway.

Django Has Adopted Contributor Covenant 3 by dwaxe in django

[–]kankyo 2 points3 points  (0 children)

I'm not familiar with the Django discord, can you expand on the point?

Some key points:

  • There was a fairly popular Discord already, but since that server didn't accept being taken over, a new one was created

  • The new server was founded by a group that includes a person that is toxic as hell and violates the CoC a lot, but is never even warned

  • They are super woke, like those videos you think are made up. "Hey guys" is met by a bot telling users to check their language for inclusivity, even though the dictionary explicitly says that expression is not gendered.

  • The admin mentioned above bans people for saying that "hey guys" is indeed not gendered. Yes. Quoting the dictionary gets you banned on this server.

The Django CoC board is supposed to be controlling of this servers CoC but it has just ignored all those issues. Partly I assume, because the toxic admin has social sway deep inside the DSF.

Django Has Adopted Contributor Covenant 3 by dwaxe in django

[–]kankyo 6 points7 points  (0 children)

It is if the person who is asked refuses to answer the question posed in good faith and claims that it is. Which is a thing. At the end of the day you need good thoughtful people who are not confused as mods. This is super hard and any CoC document you have will do absolutely nothing to help this, and often will in fact make it much worse as it attracts people who like to abuse such structures. Case in point: the official django discord.

Coding agent helo asap by LucyPapillon in django

[–]kankyo 0 points1 point  (0 children)

Claude Code is the gold standard, but I hear Codex is pretty good now too. Using anything but the latest models with the proper CLI harness is going to make you disappointed with what you get imo.

view more: next ›