On 2014-12-16 13:15, Sayth Renshaw wrote: > With django what benefit do I get for the extra build time over > Drupal or Rails. Configuration I assume but real world benefits not > my/our joy of configuration.
You're asking about two separate products. Over Rails, the feature-sets are fairly even, so it's mostly a matter of language preference. Some folks prefer Ruby and thus choose Rails, while I prefer Python so I choose Django. Regarding Drupal, that's a CMS. You can shoehorn it into providing other features, but it will always carry those CMS biases with it. While you can make your own bespoke CMS in Django (or, as Avraham wrote, use one of many pre-existing projects). I'd much rather make a domain-specific application in Django than try to hammer Drupal to my will (omitting the fact that any significant changes in Drupal require using PHP is an instant turn-off for me). One of Drupal's biggest advantages is the same as for any PHP project: deployment. For PHP projects, deployment can be done on free or very cheap hosting services (under $5 (USD) per month) and usually just involves dumping a bunch of files on a server via ftp/ssh/scp/sftp or a web interface. For Django, it requires a lot more configuration with mod_wsgi/wsgi/uwsgi/gunicorn/fastcgi/mod_python and a server that lets you have such long-running processes. -tkc -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20141216154116.7d40630a%40bigbox.christie.dr. For more options, visit https://groups.google.com/d/optout.
