Greetings Djangoers, I'm thinking of defecting from the Ruby on Rails camp because I think Django may be more in line with what I want to do. If you have a couple minutes, could you please tell me if I'm on the right track?
What I want to do =========================== Basically, I want to speed development of *websites* with applications built into them. Emphasis on the word "sites" as opposed to "applications". Almost every site I build has some element of interactivity, whether it be a simple contact form or basic shopping cart or full-on web forum. I tend to prefer building in these things myself rather than trying to wedge some 800 pound PHP monster into an otherwise elegantly coded site. I'd ultimately like to develop my own little suite of plug-in apps -- a basic forum, blog, shopping cart, etc. Then building a client's unstyled but semantically-coded working site would be totally trivial, and 90% of the work would happen after that in CSS land. That's the Grail for me ;-) Why I think Rails is the wrong tool for the job ===================================== I was really *really* excited about Rails when I first discovered it about a year ago (ask my poor wife how excited I was). But there are two things about Rails that are problematic for me. (1) Rails seems more geared towards writing single monolithic applications rather than websites with little apps built into them. I suppose I could explore the "plug-in" architecture more -- but I suspect it won't be as elegant as I'd like for building websites with mini-apps in them as described above. (2) I run my own shared servers. I need to be able to deploy 100+ sites on a single box. This is a nightmare with Rails because it hasn't had a very solid deployment platform (although maybe Apache2/Mongrel solves this). Rails also tends to eat RAM the way my mom eats cheesecake. Specifically what I'm hoping Django will do for me ========================================= (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? (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? (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? Sorry for the looong post. Any feedback at all would be very much appreciated! Cheers! Sean --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
