Live data from Hacker News

Django 1.6 beta 1 released

djangoproject.com

11–20 of 72 posts

Re: Django 1.6 beta 1 released

#11
I'm thrilled about this particular release, because it includes a significant overhaul of the way joins are built (or rather, trimmed) in the ORM and almost certainly makes your project faster if you do even relatively complex queries:

The original bug: https://code.djangoproject.com/ticket/10790

Got even worse in 1.4 https://code.djangoproject.com/ticket/18785

Thanks Anssi!

Re: Django 1.6 beta 1 released

#12
post #9

I really enjoy working with Django, but in many ways, it seems to be staying pretty vanilla while other technologies head in more experimental directions. Does Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the web world?

I personally hope django (and rails) keep their focus on the "bland corner of the web." The vast majority of (useful) sites out there are dead dull from a technology perspective, and I'd like tools that help me develop & deploy those types of sites as quickly as possible.

Exactly. I don't want exciting. I don't want magic. I want predictable. I want to be able to pump out high-functioning websites and add features where necessary. Let other libraries handle the bells, whistles, and doo-dads.

Re: Django 1.6 beta 1 released

#13
post #5

I really enjoy working with Django, but in many ways, it seems to be staying pretty vanilla while other technologies head in more experimental directions. Does Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the web world?

We've got a more complex application (Pathwright) running Django, and we're currently going much more heavy client side. Nothing about Django keeps you from doing this, and there are some excellent third party apps that actually make it very easy (django-rest-framework is awesome). > Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the w…

django-rest-framework looks good, been years since I used Django in any seriousness, so will have to give it another run. As an aside, what's the scoop on Python 2.7.X and 3.0 never likely to meet? It makes me uneasy...

Re: Django 1.6 beta 1 released

#14
I'm currently working with Django for a client's project I'm developing. Coming off a LAMP stack binge, the technology itself has been an absolute delight. I've been given the directive to use South to manage the data model, but for future projects I was hoping somebody with more experience can give some insights as to what you've found works and what doesn't work. I'm not the biggest fan of South, but maybe it's just a lack of experience/patience.

Re: Django 1.6 beta 1 released

#15
> Does Django have a bright future in a world that's moving heavily client side

Where are you getting the data for the client from? Django-Rest-Framework is a very convenient way to get data down into the browser layer from a DB.

Re: Django 1.6 beta 1 released

#16
post #14

I'm currently working with Django for a client's project I'm developing. Coming off a LAMP stack binge, the technology itself has been an absolute delight. I've been given the directive to use South to manage the data model, but for future projects I was hoping somebody with more experience can give some insights as to what you've found works and what doesn't work. I'm not the biggest fan of South, but maybe it's jus…

I would always use South, but you need to read the migrations and _understand_ what it's doing. When it gets a conflict (and it will), you need to be able to fix up the migrations.

Re: Django 1.6 beta 1 released

#17
post #14

I'm currently working with Django for a client's project I'm developing. Coming off a LAMP stack binge, the technology itself has been an absolute delight. I've been given the directive to use South to manage the data model, but for future projects I was hoping somebody with more experience can give some insights as to what you've found works and what doesn't work. I'm not the biggest fan of South, but maybe it's jus…

Unfortunately that's the best we have right now. However, the guy who wrote South (and is a core Django developer) ran a Kickstarter last month to raise funds to write South-like functionality directly into the Django core.

Re: Django 1.6 beta 1 released

#18
post #10
post #5

Earlier quoted context omitted.

We've got a more complex application (Pathwright) running Django, and we're currently going much more heavy client side. Nothing about Django keeps you from doing this, and there are some excellent third party apps that actually make it very easy (django-rest-framework is awesome). > Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the w…

he's probably referring to the ever-recurring topic of django not integrating front-end libs out of the box (which I in particular support).

I support that too, but I think Django should provide some default API endpoint support (like Django Rest Framework).

Re: Django 1.6 beta 1 released

#20

> Does Django have a bright future in a world that's moving heavily client side Where are you getting the data for the client from? Django-Rest-Framework is a very convenient way to get data down into the browser layer from a DB.

I think this is an area where ASP.NET MVC excels because, while REST is nice, you also have to consider web sockets, and I have not seen good web socket support in Django, where ASP.NET has SignalR which is loads easier to configure than a custom solution with Django and Nginx/Apache. Not to mention that SignalR has very nice degradation support on both ends when web sockets are not available.
Post reply on HN