Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 6

docs.djangoproject.com

Post reply on HN
Print view View original

91–100 of 192 posts

Re: Django 6

#91

Post by Muromec »

jorl17 wrote: post #87
Muromec wrote: post #79

Earlier quoted context omitted.

>Or there were more reasons to it? Internet was slower in both latency and throughput is one reason. The other is general tendency to separate things into smaller pieces. Faster feedback to user is the third. Consider a typical form with 10 fields in django. You define the schema on a backend, some validation here and there, a db lookup and form-level rules (if this field is entered, make the other field optional). T…

> Then somebody funds an RCE in server components. I'd say they found it, but I love the conspiracy theory :D :D :D

Something happened to my brain lately and I started to make this kinds of typos in English, which I didn't before.

Re: Django 6

#92

Post by atomicnumber3 »

haolez wrote: post #82
atomicnumber3 wrote: post #50

Earlier quoted context omitted.

Java honestly just does not have this. By the time java collectively decided that being able to spend your time writing your actual product instead of fucking with config shit forever, the age of the monolithic SSR templated backend app were gone. So now most modern things like helidon focus on being microservicey like go, or they have very soft template rendering offerings and don't really do batteries included. I f…

Isn't there Thymeleaf that alleviates that?

Forgive me, but thyme leaf is soft compared to ERB and jinja.

Re: Django 6

#93

Post by Muromec »

yoavm wrote: post #14
ianberdin wrote: post #6

Thanks to Django. I got into the webdev world so easily. Curious, how come Django started to make major versions instead of 1.*? Can be the decreasing in popularity the reason to make Something to change it?

It didn't - https://www.djangoproject.com/download/#supported-versions

It's amazing, that django docs look and feel exactly the same the did in 0.9x. Damn kids with their JS bullshit have to change the whole site between v1 and v2 and then again when v3 happens. Links rot, API index is hidden and instead of text you get a dump of TS interfaces with zero comments.

/rant

Re: Django 6

#94

Post by jorl17 »

Muromec wrote: post #91
jorl17 wrote: post #87

Earlier quoted context omitted.

> Then somebody funds an RCE in server components. I'd say they found it, but I love the conspiracy theory :D :D :D

Something happened to my brain lately and I started to make this kinds of typos in English, which I didn't before.

I'm 32, but I noticed I started making similar mistakes around 28 or so. Occasionally I write out words which are completely wrong, but sound similar.

It's as if one part of the brain is doing the thinking, and another one is "listening" to it and transcribing/typing it out, making mistakes.

For a little while I was a bit worried, but I then realized nothing else had changed, so I've just gotten used to it and like to jokingly say "I've become so fast at thinking that even I can't keep up!"

Re: Django 6

#95

Post by Muromec »

zelphirkalt wrote: post #57
mamcx wrote: post #37

Earlier quoted context omitted.

Because JS is bad, and JS have a MASSIVE user base, so whatever they do is the web. And because JS is on the frontend, solutions are front end , even the ones that eventually run on the (js) back-end. Is like how people use a RDBMS but never do foreign keys, views, etc and re-invent all, poorly.

I had similar thoughts, but how does one use an RDBMS without making use of FKs? Do they put all in one huuuge table, that has all the columns and is super sparse? Or some other fever dream of bad design?

You can have a field with some value that just happens to match the id in a different table. That something could be a foreign key or just a number.

Re: Django 6

#96

Post by 0xblinq »

Genego wrote: post #73

Django has been one of the biggest reasons why web development has been so enjoyable to me. Whenever I switched to something else, I just felt too spoiled by everything that Django gives you. So I always ended up back with Django, and have no regrets at all specializing deep down that path.

That’s true as long as you are only talking about the backend.

Frontend wise, Django is in the Stone Age.

Look at Laravel or rails if you want a really complete full stack solution.

Re: Django 6

#97

Post by Muromec »

jorl17 wrote: post #94
Muromec wrote: post #91

Earlier quoted context omitted.

Something happened to my brain lately and I started to make this kinds of typos in English, which I didn't before.

I'm 32, but I noticed I started making similar mistakes around 28 or so. Occasionally I write out words which are completely wrong, but sound similar. It's as if one part of the brain is doing the thinking, and another one is "listening" to it and transcribing/typing it out, making mistakes. For a little while I was a bit worried, but I then realized nothing else had changed, so I've just gotten used to it and like t…

I suspect that as I got more vocabulary (and more languages) and started to actually speak the language more, I remember the "sound" of the word where I used to remember the spelling before. Like "it's" and "its" wasn't a problem before, but now I catch it somewhere in the text. At least I consistently write more than 50% of the articles nowdays. Languages are weird.

Re: Django 6

#98

Post by megaman821 »

BowBun wrote: post #62
stevex wrote: post #31

One thing Django has going for it is that the "batteries included" nature of it is perfect for AI code generation. You can get a working site with the usual featuers (admin panel, logins, forgot reset/password flow, etc) with minimal code thanks to the richness of the ecosystem, and because of the minimal code it's relatively easy for the AI to keep iterating on it since it's small enough to be understandable in cont…

Ruby and Rails are even better candidates. CSP, Background workers, and many other features that Django still lacks have been standard offerings for sometimes 10+ years!

Rails tries to more tightly integrate with the front-end which causes a lot of turn over the years. Django projects from 10 years ago are still upgradable in a day or two. Rails does include some nice stuff though, but I much prefer Django's code first database models than Rail's ActiveRecord.

Re: Django 6

#99

Post by risyachka »

throwawaymaths wrote: post #38
stevex wrote: post #31

One thing Django has going for it is that the "batteries included" nature of it is perfect for AI code generation. You can get a working site with the usual featuers (admin panel, logins, forgot reset/password flow, etc) with minimal code thanks to the richness of the ecosystem, and because of the minimal code it's relatively easy for the AI to keep iterating on it since it's small enough to be understandable in cont…

why would you need batteries included? the ai can code most integrations (from scratch, if you want, so if you need something slightly off the beaten path it's easy

Its literally the opposite.

Why would you generate sloppy version of core systems that must be included by default in every project.

It makes absolutely zero sense to generate auth/email sending/bg tasks integration/etc

Re: Django 6

#100

Post by kstrauser »

acdha wrote: post #54
throwawaymaths wrote: post #38

Earlier quoted context omitted.

why would you need batteries included? the ai can code most integrations (from scratch, if you want, so if you need something slightly off the beaten path it's easy

What’s more likely to have a major security problem – Django’s authentication system or something custom an LLM rolled?

I don't even particularly care for Django, but darned if I'd want to reimplement on my own any of the great many problems they've thoroughly solved. It's so widely used that any weird little corner case you can think of has already been addressed. No way I'd start over on that.
Post reply on HN