11–20 of 76 posts
For anyone who considered Django and discarded it (especially recently since it's been 1.0), could you maybe explain the decision behind that? I'm curious as a relatively recent Django convert.
That makes it a non-starter for us (for now).
Would someone that up'd Django please outline their plans to scale?
Django scales just like any other web framework. The plan to scale Django is roughly the same as the plan to scale any app. Are there any issues in particular you're concerned about?
For example, did you modify the source to support multiple databases for read/write? Or is that not an issue and it's OK that it's coming later in the framework's roadmap?
Wait... there are people who wrote their own framework... in the year 2009?
http://docs.djangoproject.com/en/dev/faq/general/#why-does-t...
But I still see it a lot, there's a lot of "not invented here" or "none of the existing frameworks do exactly what we want".
Would someone that up'd Django please outline their plans to scale?
* squid reverse proxies
* memcached
* low memory footprint httpd serving static content (e.g. nginx / lighttpd etc.)Wait... there are people who wrote their own framework... in the year 2009?
it's a bit of development overhead in the beginning, but pays of in the long run.
Why the heck is Grok listed, but not Zope?
Earlier quoted context omitted.
Django scales just like any other web framework. The plan to scale Django is roughly the same as the plan to scale any app. Are there any issues in particular you're concerned about?
Have you listened to Cal Henderson's friendly rant against Django from a scalability perspective? http://www.youtube.com/watch?v=i6Fr65PFqfk For example, did you modify the source to support multiple databases for read/write? Or is that not an issue and it's OK that it's coming later in the framework's roadmap?