On 12 nov, 01:16, shacker <shac...@birdhouse.org> wrote: > I've just put up a > pretty complete draft of a post on this topic, written with decision > makers (managers, supervisors) in mind. It's still probably somewhat > technical for that group, but that's the nature of the topic. > > http://birdhouse.org/blog/2009/11/11/drupal-or-django/ > > > Feedback and further contributions welcome. >
A couple things that came to mind while reading your draft: 1/ wrt/ performances AND rapid development : I recently had to work on a not-so-complex (functionaly-wise) Durpal project, and the response times on my local station - all caches disabled of course - turned the development process into a sluggish nightmare. Never had this kind of problems with Django, even for far more complex apps. 2/ wrt/ rapid development again: I started yesterday afternoon (on my spare time) a simple virtual gallery application for a painter friend of mine. I had more than half of the application (including templates etc) working in a couple hours, and most of the still missing features will be provided by existing pluggable djang apps. It shouldn't take more than a couple more hours to have the whole thing up and running. And when I say "a couple hours", I really mean it, litteraly !-) Else, I just can second most of the developper's comments : from my experience, it can take more time doing "simple customisations" on Drupal than you'd need to implement the same features from scratch in Python. My 2 cents. -- 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=.
