On Thu, Dec 3, 2009 at 11:42 AM, Todd Blanchard <tblanch...@mac.com> wrote: > Django has several superior features to rails that drive me to use it. The > admin is much better than active scaffold, there are a number of already > written apps, geodjango postgis integration, scalability, etc..... > > That doesn't mean I have to think it is superior in every way and when its > not, I'm apt to point them out. No good idea should go unstolen IMO.
wholeheartedly agree > I'm going to stick with preferring convention over configuration. If I want > to write boilerplate over and over I'll use J2EE. :-) violently disagree. any hardwired convention is a straightjacket. if you have repeated code, write a shortcut (it's pretty easy), just don't make it the default. > I've solved my urls problem for now (though I'm open to more elegant > solutions) but I think not having a default url scheme is lame. Rails has > routes which means you can rearrange the url patterns anyway you like, just > like django. In practice this is mostly a waste of time and you just use the > defaults. That doesn't mean I have zero custom routes in all my apps, but I > have very few because the defaults are so well chosen. Django, OTOH, > provides no sensible default url scheme at all out of the box. I don't see > that as a feature, its a pointless time drain. have you considered writing a url pattern generator? if it's handy enough, it would become quite popular... -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
