James: > I think the directories Rails creates might represent best practices > for Rails use, but I'm not at all certain that they represent best > practices for anything other than Rails.
Well, I don't see how Django couldn't benefit from best practices for, e.g., staging, testing, documentation, and a place to put 3rd-party stuff. The other arguments basically comes down to a tradeoff between being easy to get started and easy to keep going (and finish). I think Django, like RoR, can support both, but is currently suffering a bit compared to RoR: * ease of getting started * non-traditional architecture and overloaded the 'view' term * can't generate model from database * cool screencast * ease of finishing * lack of best practices
