On Wed, Jun 16, 2010 at 5:26 PM, finn <finngruwierlar...@gmail.com> wrote: > Hi, > > I have with interest followed the thread "Seeking Django vs. Joomla > comparison", and it has inspired me to start this new thread. > >.... > > Let me end this post with a comment to the "compare-apples-with- > oranges"-thing that I hear so often: every programmer knows that > "apples" can be compared with "oranges". Since "o" has a higher value > then "a" in most encoding systems, "oranges" > "apples". What we need > to do is simply to convince people that the flexibility and code > cleanness they get with Django gives them much more value than all of > the 1000+ Drupal modules together. > > I think that was all... > > Finn Gruwier Larsen >
This kind of discussion comes up frequently whenever there are people who like a bit of software, they get used to using one particular bit of software, and start to think that that bit of software is so clearly the best that choosing another bit of software is "wrong" and their way is "better". Different tasks may require different tools, and just because one knows a particular tool extremely well, they think it should be used for all of them, where as it is usually more accurate that many different tools can produce an effective solution. The most important thing for any project manager is that they know precisely why they are using a particular tool. You should be able to justify to yourself why to use a particular tool, and the answer is never "it's better". For instance, on one of my projects we are using django. Why are we using django? 1) Django is written in python, python is quick and easy for programmers to learn, lots of job applicants (profess to) have python skills. 2) Django has an elegant structure of middleware and context processors that allow us to modify/update important parts of the web stack. 3) Django has a sane template system, not based on XML (use ZPT/XSLT for a while, see what I mean :) 4) Django has useful 3rd party apps we can use to shorten development time, eg django-rosetta for our translators to update translations, django-south for managing database structure, contrib.auth and contrib.admin. 5) We have resource to maintain development on this project For other projects, eg our wiki, blogs, bug tracking and vcs we use COTS software (well, Open Source Off The Shelf perhaps may be more accurate), because we don't want to spend the time maintaining/updating/improving these applications, we just want them to work (hacking them until they work). This is a long way of saying "Just because you can write a CMS in django, you probably shouldn't". Unless your goal is developing a CMS in django, you will waste time you could be doing useful things in! Cheers Tom -- 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.
