On 7/20/06, Sean Schertell <[EMAIL PROTECTED]> wrote: > (1) Portable apps across projects architecture. From what I've read, > it sounds like a perfect fit for what I want to do. Is it really that > great?
Yes. It is that great. :) It's really interesting that you see that as one of Django's main strengths, as it's something we don't really advertise (but we should!). The software from which Django was extracted -- a news package called Ellington -- was designed to let apps be portable across projects/servers/sites. We wanted to be able to say "Let's reuse this events-calendar thing on Lawrence.com and LJWorld.com, giving them different templates for the different sites, but keeping the same backend code." It's exactly what you're looking for, in that respect. And thanks for indirectly encouraging us to advertise this feature more... > (2) Stable deployment with mod_python instead of some wonky FastCGI > jalopy. Is it *really* stable -- enough for mission critical > production environment? How about memory footprint? Can I run 100+ > Django sites on a shared server and expect smooth sailing? It's production-ready. I'm using it at washingtonpost.com -- see, for example, projects.washingtonpost.com/congress -- and various organizations use it for "mission critical" sites. Check out http://code.djangoproject.com/wiki/DjangoPoweredSites for plenty of examples. > (3) I still get to keep most of what I love about Rails. Pure object- > oriented MVC (MTV) development stucture, free stuff like form > validation, code generation, pagination, input sanitization, etc. Is > it true? What will I miss most about Rails? Here's something Rails has that Django doesn't have: the requirement to write "end" statements. :) But seriously... I've never used Ruby on Rails, but the "feature" that people say Django doesn't have, that Rails does, is automatic Ajax JavaScript generation. I put "feature" in quotes because I personally don't see much value in automatically generating JavaScript, anyway. Other than that, Django doesn't create any stubs for unit tests, so if you're accustomed to writing unit tests for your Web applications, you'll have to set them up by yourself rather than using any sort of integrated thing. (However, we're close to adding easy testing support -- see http://code.djangoproject.com/ticket/2333 .) And you can use any number of excellent Python unit-testing libraries on your own. Hope this helps, Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
