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

Django 1.9 Released

djangoproject.com

Post reply on HN
Print view View original

11–20 of 91 posts

Re: Django 1.9 Released

#11

Post by jsmeaton »

This might be a good time to mention that Django is always trying to raise funds: https://www.djangoproject.com/fundraising/

The really quick turn around on tickets and pull requests is largely thanks to the Django Fellow, who is paid to manage the community. The last two or three releases have been on time because of the Fellow. The Fellow is funded via Django Software Foundation fundraising activities.

If your company is deriving financial benefit from using Django, consider asking your company to sponsor the fellowship program, so that we can ensure that bugs are getting fixed, releases are happening on time, and security releases are being processed as a priority.

(Disclaimer: core member).

Re: Django 1.9 Released

#12

Post by sparkling »

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

Re: Django 1.9 Released

#13

Post by jsmeaton »

sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

If you like Ruby, Rails.

If you like Python, Django.

Both are full featured with active communities. The 10,000ft view of each is very similar.

Re: Django 1.9 Released

#14

Post by nine_k »

sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

For a small project I'd take Flask :)

Re: Django 1.9 Released

#15

Post by dguaraglia »

sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

I'll give my stock response when this question comes out: the reason why I chose Django back in the day (we are talking pre 1.0) was because it stuck with the Python philosophies of configuration-over-convention and "principle of least surprise".

It made debugging issues much easier than in the equivalent Ruby on Rails project (I tried to build the same proof-of-concept using both frameworks.) When something broke in Django I could usually just follow the code to find what was wrong. With RoR sometimes I would put stuff in some place, expect the framework to pick it up (convention-over-configuration) and the code wouldn't work. Much head scratching ensued.

Re: Django 1.9 Released

#17

Post by throwaway_ghj »

sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

Are those options the state of the art?

I wouldn't use either.

Edit: added the following...

I've dabbled with both, and they suffer from the same kind of problem that all frameworks on top of dynamic languages suffer from. You essentially have to do all the checks that the compiler /should/ do for you, by using unit tests. That gets old fast. Also, on large code bases, I now prefer having real refactoring support.

I'd rather pick something on top of a compiler that is not brain dead.

If I had to do python again, I'd use pyramid or flask, and if I had to do ruby, I'd look at Sinatra.

I stand by my original statement, on the basis that both of the offered frameworks are built upon shaky ground to start with.

Re: Django 1.9 Released

#18

Post by sauere »

throwaway_ghj wrote: post #17
sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

Are those options the state of the art? I wouldn't use either. Edit: added the following... I've dabbled with both, and they suffer from the same kind of problem that all frameworks on top of dynamic languages suffer from. You essentially have to do all the checks that the compiler /should/ do for you, by using unit tests. That gets old fast. Also, on large code bases, I now prefer having real refactoring support. I'…

Care to elaborate?

Re: Django 1.9 Released

#19

Post by [deleted] »

sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

[deleted]

Re: Django 1.9 Released

#20

Post by Thaxll »

throwaway_ghj wrote: post #17
sparkling wrote: post #12

Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?

Are those options the state of the art? I wouldn't use either. Edit: added the following... I've dabbled with both, and they suffer from the same kind of problem that all frameworks on top of dynamic languages suffer from. You essentially have to do all the checks that the compiler /should/ do for you, by using unit tests. That gets old fast. Also, on large code bases, I now prefer having real refactoring support. I'…

Nice troll.
Post reply on HN