3 ms·
I worked with both Rails and Django and I like Django's approach better ... simply because the fields declaration is higher-level. I.e. you don't have a "filep
by bad_user 16y ago
I worked with both Rails and Django and I like Django's approach better ... simply because the fields declaration is higher-level.
I.e. you don't have a "filepath varchar" field, but a "photo=ImageField(thumbnail_size=[320,200])".
I've had a good experience with South for database migrations, used it in every Django project I tried ... the only things bothering me is that the generated files are too verbose (not much of a problem, since you don't need to modify the auto-generated code), plus a migration-based system doesn't really blend if you've got multiple apps in the same project (refactoring becomes painful).
Other than that, Rails is pretty good because of its declarative APIs. Django has too much boilerplate for my taste ... but I like that for complex projects where I need to tweak things.