Thanks for presenting a different angle. I imagine you're one of these long-bearded guys who uses NetBSD and Fluxbox as his main desktop OS and edits code in VI through a tsch shell ;-)
For me? OS X and TextMate plus some well thought-out framework that allows me to get from A to Z in __as little time as possible__. I'll re-invent stuff if necessary, but if there's some well-oiled machine that I can find to do exactly what I want, I'd much rather use that. Polish and cohesiveness are important to me. I'm allergic to "jalopy" solutions with various bits all taped and stapled together (cough - desktop Linux - cough). So for me personally, I think a framework born of a single vision such as Django or Rails is a better fit. But I'll bet you the guy sitting next to me would jump all over your idea :-) Sean On Jul 21, 2006, at 10:56 AM, Elver Loho wrote: > > Allow me to offer a dissenting view. I recently faced the task of > finding a Python-based framework to use at work and tried several, > including Django. I finally settled on using CherryPy with Kid. (Which > is what TurboGears is doing, but with a lot of extra cruft thrown in. > And btw, the TurboGears mailing list is great for tech support on > CherryPy and Kid.) > > On 7/21/06, Sean Schertell <[EMAIL PROTECTED]> wrote: >> 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? > > In CherryPy, every "directory" of the website is mapped to a class > with its exposed methods being the "files" in that directory. It's a > godsend as you can write any kind of functionality (shopping cart, > blog, whatnot) into a class or two and plop it anywhere else. Very > portable and versatile. > > Django is somewhat more flexible (as you can map any function to any > path), but CherryPy's class/method way of mapping things suits me > better. It just seems more logical. Whereas Django allows you to > redefine logic if needed :P > >> (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? > > CherryPy provides its own server by default, which according to the > CherryPy website is very stable, mature, and fast (with raw speeds > comparable to Apache) but I think it can be set up using mod_python. > Because Apache is faster for serving static files, we have CherryPy on > a soon-to-be-in-production site sitting behind mod_rewrite so that > certain folders are served by Apache. > >> (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? > > If you want OO, then from what I've seen, CherryPy might be a much > better choice. As for free stuff, then Django certainly does all that > (except code generation) and TurboGears does all that, (except code > generation) but CherryPy alone does not. > > You could use the form validation, input sanitizaion and other needed > tidbits from TurboGears. If you want them. (I really didn't need them > on our CherryPy system. I'm one of those people who likes to reinvent > bikes for fun :P) > >> Sorry for the looong post. Any feedback at all would be very much >> appreciated! > > Before anyone flames me, then I think Django is great. It's a lot of > fun to develop with and it's certainly a very capable framework with a > lot of interesting new features I hadn't seen before. But it just > didn't "click" for me. CherryPy seemed more mature, more stable, more > minimalistic, and certainly more in tune with my programming style. > > But hey, I'm no expert :) > > > Elver > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
