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

Django 2.1 released

docs.djangoproject.com

Post reply on HN
Print view View original

51–60 of 129 posts

Re: Django 2.1 released

#51

Post by txcwpalpha »

jtchang wrote: post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

Are there people going around saying that Django is obsolete? I've seen a lot of people argue against using Django in favor of RoR or Flask, but that's usually based on personal preference. I've never seen anyone say that it's "obsolete".

Re: Django 2.1 released

#53

Post by Alir3z4 »

OmarGonzalez wrote: post #48
jtchang wrote: post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

Why would anyone consider it obsolete to begin with ? If anything, I would consider someone making that statement miss informed

I would consider that person to be obsolete :D

Re: Django 2.1 released

#54

Post by strig »

oneweekwonder wrote: post #39
akx wrote: post #28

Earlier quoted context omitted.

Sure you can. See the documentation: https://docs.djangoproject.com/en/2.0/ref/contrib/postgres/f...

Thank for the quick reply. Now I need to understand how the "__" magic work; And I wonder what would django do if my key is "animal__breed". Will it understand: Dog.objects.filter(data__animal__breed='collie') But this is maybe questions I should rather ask on #django or stackoverflow.

Django won't let you name a model field with a double underscore, I believe. Not sure how this would work with a Postgres JSON type column though, but it would probably throw an error.

Re: Django 2.1 released

#55

Post by Alir3z4 »

appleiigs wrote: post #50

A reminder to support these guys! 24% funded and they’re only asking for $200K. :( https://www.djangoproject.com/fundraising/

Thanks for mentioning. I was going to post that I see you did it already.

Such a heavy mega framework that small to big companies and individual relies on, we should support it.

Whoever sees this, please support Django to reach its goal.

Re: Django 2.1 released

#56

Post by paulddraper »

OmarGonzalez wrote: post #48
jtchang wrote: post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

Why would anyone consider it obsolete to begin with ? If anything, I would consider someone making that statement miss informed

There are not currently many well-known products that use it. (Bitbucket cloud being the exception.)

That's not the best of reasons; just because Django is not used by Google doesn't mean it isn't the perfect tool for you.

Re: Django 2.1 released

#57

Post by djsumdog »

zimablue wrote: post #24
fredley wrote: post #7

I've been working with Django for almost my whole career, since 1.1. It's a joy to use, and blows any other web framework I've used out of the water when it comes to actually just building stuff. Django is a fantastic boring[1] tool, and seeing boring updates like this is great. 1: http://mcfunley.com/choose-boring-technology

As a counter point, I tried to use Django for a data-visualisation project and ran into some problems. Everything is built on models, which are kind of activerecord pattern. Django has an inbuilt (and inferior) version of sqlalchemy, so that when you want to push sql past a certain point (define queries more complex than the api) you're pretty much stuck. Now you have codebase with two different database libraries in…

I mean that's a general problem with ALL ORMs. I've been on Django projects where we had to drop down and pass raw SQL statements.

On my current project we don't use an ORM; just SQL statements and we create classes to match the result set and map into them.

Re: Django 2.1 released

#58

Post by dopeboy »

keshab wrote: post #8
theptip wrote: post #6

Read-only model views are a great addition to the Django admin -- I've been watching that PR for a long time, glad to see it land. This will make it a lot easier to build internal admin dashboards that are safe to share with non-privileged users like support staff.

I have seen a bastardized version of Django admin used as a quite sophisticated dashboard. This new addition will make it even easier to hack together things like that in a very short time.

This is a surprisingly pretty common practice. I know people, even at Google, who want the ease of CMS but additional control.

Re: Django 2.1 released

#59

Post by 52-6F-62 »

jtchang wrote: post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

At work because I have lately needed to roll web server/api/admin/client apps (embellished CRUD situations with some other serverside processing to generate user output) and for those my go to for dev speed, platform speed, familiarity, and a few other concerns I generally go with Node/Express/TypeScript and it's great to work with.

However for my personal site I used Django to give it a shot. Once I wrapped my head around a couple of different paradigms it was quite nice to work with, though I probably haven't laid it out as well as I would a real product or tool. It was very easy to get a pretty basic blog set up.

My only gripe might be on the blog end— it was kind of a pain to find a halfway-current compatible text editor for that purpose. But that isn't the end of the world for my own site. And of course, that's not an issue with Django itself.

Re: Django 2.1 released

#60

Post by txcwpalpha »

paulddraper wrote: post #56
OmarGonzalez wrote: post #48

Earlier quoted context omitted.

Why would anyone consider it obsolete to begin with ? If anything, I would consider someone making that statement miss informed

There are not currently many well-known products that use it. (Bitbucket cloud being the exception.) That's not the best of reasons; just because Django is not used by Google doesn't mean it isn't the perfect tool for you.

Instagram uses it. I'd say they're pretty well-known.

Others: DigitalOcean, Pinterest (used Django at first, may have moved to Flask by now, not sure), Mozilla, Disqus, Robinhood, The Washington Post.

Post reply on HN