Re:Ask HN: Where is the Django community?
by andybak on Monday July 18, 2011 @06:26PM
(#2778603)
"a third party application that isn't baked into the framework." In what way is this a bad thing? South has excellent support, code-quality and usage. The only thing that would change by building it into Django would be to tie it's release schedule to that of a much larger code-base.
[ Parent
| on HN ]
Re:Ask HN: Where is the Django community?
by endlessvoid94 on Monday July 18, 2011 @06:41PM
(#2778684)
Heh, I'm not bad mouthing south at all. If it didn't exist, I wouldn't use Django at all. Thank god for south.
But I'm using Django DESPITE the fact that I have to use south. Contrast this with Rails, which FORCES you to use migrations (last I checked).
Why would I want to be forced to use South? There are other migration methods that approach the problem different ways, or perhaps I want to write my own?
Third part != Lower quality. In this case, it means being able to make incremental improvements outside of the Django release schedule. So while Rails bakes it in and forces a release schedule on migrations, South isn't encumbered by this, and is more agile.