Hacker News Reader

I like Django quite a bit, but the mind boggles at how many developer hours have been spent trying to organize settings, or deal with migrations, or setting up deployment scripts, or coming up with a sensible project layout.

I mean, doesn't everyone have to solve these problems for almost every project? Django seems to try too hard not to make decisions for you, when it would make more sense to make easily ignored decisions.

View on HN

> how many developer hours have been spent trying to organize settings, or deal with migrations, or setting up deployment scripts, or coming up with a sensible project layout

Countless. Django prefers configuration over convention. I think it's because there is too much focus on the reusable apps concept. It would be great if it was a little bit the other way around.

Are there still issues with migrations, or are you referring to Django's past? South migrations work smoothly for me.

The fact that you have to install South to begin with is an issue, IMHO.

Django had a project accepted to Google Summer of Code 2011 to get some schema migration love into core, so the future looks good, but if you ask me 'pip install south' isn't that much of an issue.

Reply on news.ycombinator.com