On Saturday 31 October 2009 10:42:24 Andy McKay wrote: > One key thing to remember is that Django and Drupal (and the other > things you mentioned) are quite different things. You are comparing > apples to oranges which makes the sell harder. > > Drupal is a CMS and has a different target audience. It has the level > of complexity that comes from solving the CMS problems. > > Drupal like most CMS's will allow you to do things the Drupal way > quite easily. As soon as you stray from that path, you'll be in trouble. > > I recommend understanding your audience and the difference in tools > and how this affects them. > -- > Andy McKay > www.clearwind.ca
This is very true, but he can sell it as a cms with one of the many cms for django[1]. Here he can pick one that matches the known requirements the managers are looking for, then sell django along with the cms. After that there are really only three main selling points, customization, django has plenty of prebuilt apps[2] and the ability to build your own app with ease. Secondly, speed of development, all php needs is header files to be a poor mans version of C. Django has made making web apps almost trivial and the most time I spend now, is on the ui (both dojo and jquery make this almost trivial also), rather than the backend. Finally, there is the maturity of the language. PHP is still adding in features other, similar languages already have had. For example namespaces are just barely a year old in php, initial release in the dev versions, less than 6 months for the actual first appearance in a stable release. To quote wikipedia[3] on missing features from PHP: "PHP currently does not have native support for Unicode or multibyte strings; Unicode support will be included in PHP 6 and will allow strings as well as class, method and function names to contain non-ASCII characters." Seriously, in todays global world and well, for the past what 10-15 years, hasn't this been mandatory? I do not understand why web developers who use php, still do. I don't understand why companies and schools support it. When there has been other better languages to use, python, perl, java and haven't changed as much as php has and still have more, better, what I call mandatory features, plus better or equal performance. Well I do understand how it happened at first and recognize it's not going anywhere. I just wish it would go back to the toy bin/kindergarden for web developers to understand the nature of dynamic web pages. See the wikipedia page for related security topics also. The only strength php has that I believe is a strength and a weakness is it's drag and drop install. It's a weakness the same reason php security is, bad web developer choices, like storing include files and other files with sensitive information in web accessible directories. (Who remembers the inlcude() hack or fread on a remote url?) This is my main argument; the ability/maturity of the language itself. I do think that a lot of people who use php are smart individuals and just make honest mistakes that led to phps bad repution in security. But, by default, because of the intelligence of the django devs in getting this part right, that it is harder for new developers to make similar security mistakes. Really only in a few places allow you to. The reason I came to django, because of the language it's based in. Though many a day I wonder how django would do as a C++ framework. I may find out one day, but not in the near future. Mike [1] http://code.djangoproject.com/wiki/CMSAppsComparison [2] http://djangozen.com/ [3] http://en.wikipedia.org/wiki/PHP P.S. quoting me is fine, but I think the wiki page and links will make a better impression, so I suggest paraphrasing me if you find any of this useful. -- Anyone who cannot cope with mathematics is not fully human. At best he is a tolerable subhuman who has learned to wear shoes, bathe and not make messes in the house. -- Lazarus Long, "Time Enough for Love"
signature.asc
Description: This is a digitally signed message part.
