Live data from Hacker News

Django 2.2

djangoproject.com

131–140 of 257 posts

Re: Django 2.2

#131

What I find most curious about Django/Python is that about 30% of the new installs are for legacy Python/Django (2.7/1.11): $ pypinfo --start-date 2019-01-01 --end-date 2019-03-31 -- percent --markdown django pyversion Served from cache: False Data processed: 160.22 GiB Data billed: 160.22 GiB Estimated cost: $0.79 | python_version | percent | download_count | | -------------- | ------: | -------------: | | 3.6 | 39.…

Bitter clinger to 2.7 here.

I'm sure the IPv6 group expected the world to have migrated more quickly, too.

Re: Django 2.2

#132
post #80

What I find most curious about Django/Python is that about 30% of the new installs are for legacy Python/Django (2.7/1.11): $ pypinfo --start-date 2019-01-01 --end-date 2019-03-31 -- percent --markdown django pyversion Served from cache: False Data processed: 160.22 GiB Data billed: 160.22 GiB Estimated cost: $0.79 | python_version | percent | download_count | | -------------- | ------: | -------------: | | 3.6 | 39.…

Trying to move, but it's tough. Old codebase, lots of deps, and no real benefit to upgrading to 3.6, nothing our end users will care about or notice (or pay for). Upgrading to Python 3 is a chore. We have to do it, but it's not fun and it's barely useful.

I would argue py3 has negative utility for that reason. Plus, the mess of 3.5 vs 3.6 vs 3.7.

Re: Django 2.2

#133
post #129
post #125

Earlier quoted context omitted.

accusing me of ignorance while not providing a single argument is the ignorance itself EDIT: keep downvoting me, maybe downvoting the truth on a website will hide your technical mediocrity some day

Feel free to substantiate your claims. Even after your edit it's just a bunch of big claims with no supporting evidence for the things which aren't simply wrong (e.g. “no nesting, all routes have to be declared in one place” sounds like you haven't ever used a Django app, including the built-in ones. Perhaps there's something else you have in mind but since you didn't explain, who else can tell?). Lobbing insults won…

I made 9 arguments and you claim I am not even trying? good luck with your career, if you have any

Re: Django 2.2

#134
post #85

Whenever I see people still praising Django in 2019, I immediately know that their technical understanding of the current backend and ops technologies is years behind. Django is still okay for small and amateur projects but nothing more than that. It is a curse for a fast moving business. EDIT: even though I stopped writing Django for 3 years now but here are some of my reasons as far as I can remember: 1. mediocre r…

You guys hate, but he is right and you know it. In year heart you feel this call, this.. twinge. You know this is not the True Path.

I've done it both. Our Go + Angular project slaughtered Django and now I was dealing with services running at 25MB RAM with single digit CPU usages instead of the disgusting gluttons that Python and Ruby produces with memory usage measured in GBs. Production servers can have specs rivalling Raspberry PIs instead of IBM Blue Genes. Quite refreshing.

The illusion of power that Django (and all fat frameworks) create works OK if you work with a narrow set of very specific web applications in a static environment with a team of Django specialists. Anything else and the project turns to shit.

Re: Django 2.2

#135

Earlier quoted context omitted.

> - A huge ecosystem of libraries for everything from data science to email processing, that are (mostly) easy to read and modify and free from systemic security issues. And pretty much every major company with an API has an official Python library for that API. I disagree about this, there's not even a basic user signup flow plugin with page templates that would allow SSO and U2F, it was so when I was looking at it…

There was a mailing list discussion about building U2F into Django, and I agree that should get done. I don't know a ton about SSO, although I'm more skeptical about building it into Django only because there are many different ways you might want the business logic to work, so to me that suggests using a library for that might be more appropriate than having it built into the framework.

There's not even a good 3rd party library, I spent like a day testing all of them out and it's so cumbersome compared to what I had to do with Flask-Security and Flask-Dance.

Re: Django 2.2

#136
post #133
post #129

Earlier quoted context omitted.

Feel free to substantiate your claims. Even after your edit it's just a bunch of big claims with no supporting evidence for the things which aren't simply wrong (e.g. “no nesting, all routes have to be declared in one place” sounds like you haven't ever used a Django app, including the built-in ones. Perhaps there's something else you have in mind but since you didn't explain, who else can tell?). Lobbing insults won…

I made 9 arguments and you claim I am not even trying? good luck with your career, if you have any

[deleted]

Re: Django 2.2

#137

I love Django. I've used it for the last 8 years. I'm happy to see the project is still thriving. At this point, for me Django is pretty much synonymous with Django REST framework ( https://www.django-rest-framework.org/ ). I can't imagine a better API than Django w/ REST framework. For static sites I use Django's templates. Otherwise, I just use Django w/ REST framework for my API, and to serve up index.html. My ind…

I do wish Django REST Framework shipped with faster serializer code.

Re: Django 2.2

#138
post #133
post #129

Earlier quoted context omitted.

Feel free to substantiate your claims. Even after your edit it's just a bunch of big claims with no supporting evidence for the things which aren't simply wrong (e.g. “no nesting, all routes have to be declared in one place” sounds like you haven't ever used a Django app, including the built-in ones. Perhaps there's something else you have in mind but since you didn't explain, who else can tell?). Lobbing insults won…

I made 9 arguments and you claim I am not even trying? good luck with your career, if you have any

Could you please stop? Flamewars are just what we're trying to avoid on HN. When accounts behave like this we eventually have to ban them.

https://news.ycombinator.com/newsguidelines.html

Re: Django 2.2

#139

The projects/app relationship never 'clicked' with me. I also have a dislike for the awkward 'polls' example in the django tutorial. That said, I like Django. Of course, I liked Rails better, but maybe that's because it was my 'first' and I never used any of the big php frameworks for a long period of time. I quit wasting my time with Flask for projects a while ago. It's a really great project and suited for smaller…

I feel the same way. Does any one have a good overview on how the community actually separates functionality into “apps”? I have been looking at a rails like framework in python called Masonite. Does anyone in the python/Django community think this will gain traction?

They're just modules by another name.

The way I think about design is usually centered around the data model, so if some subject has a number of ORM models and is pretty self contained it makes sense to put them in their own app, together with related urls and views and stuff.

They still live in the same repository and aren't meant to be re-used, just split into logical parts to make the code base easier to think about. Modules, in other words.

Re: Django 2.2

#140
post #136
post #133

Earlier quoted context omitted.

I made 9 arguments and you claim I am not even trying? good luck with your career, if you have any

[deleted]

Please stop also. Flamewar is not what we want here, and https://news.ycombinator.com/item?id=19545921 was as much a violation of the site guidelines as the comments you're criticizing.

If someone is wrong, provide correct information and move on. If a comment breaks the guidelines, flag it and move on. In egregious cases, you're welcome to email us at hn@ycombinator.com. But please don't respond in kind or perpetuate spats.

Post reply on HN