On 9 avr, 18:06, UnclaimedBaggage <baynej...@gmail.com> wrote: > > WHAT I LIKE ABOUT DJANGO > * I LOVE django-admin . For the sort of work I do, which is a lot of > customised cart/cms stuff, this would save a lot of time. > * Code reusability seems superior. Opinions?
Not enough experience with Rails to comment on this, but good results with django so far - we do use quite a lot of 3rd part pluggable apps. > * Better perfomance? Well, there's no simple "yes or no" answer on such a question. Point is that 1/ there are quite a few stories around about scaling problem with Rails and 2/ Django's architecture seems to allow for way more possible solutions here. Now honestly, the bad stories about Rails scalability are about 2+ years old so they may have done something about it, and I never had a need for even simple caching in a Django app so far so I just can't tell from experience how well it really scales. > * I've half-built a shopping cart app in Django that I'm happy with. Did you have a look at Satchmo ? > WHAT I LIKE ABOUT RAILS > * I prefer the syntax > * There seems to be a lot more work for rails...with better pay FWIW, we have hard time hiring a competent Django developper here. But if you go that way, then there's probably even more work for PHP or Java !-) > * "Agile Rails" is a damn fantastic book. Is that a GoodEnough(tm) reason to choose one solution over the other ? > I haven't found much Django > documentation I've enjoyed as much > * Seems to be a little simpler Err... I beg to disagree here. Much more black magic in Rails. So yes, Django is a bit more "explicit" (hence more verbose), but for anything but the most trivial app it ends up being a GoodThing, as it gives you much more control on what's going on. > * Seems to have a greater depth of features > * Better AJAX integration from what I've seen Django is *by design* mostly agnostic here, and that's a very sound design choice IMHO. At least you are free to use any js lib you want and have full control on how this ajax stuff is implemented. >From a practical POV, I had no problem doing AJAX stuff with Django, be it with Prototype, JQuery, YUI or homegrown javascript code. Ok, any other consideration set aside, each of these frameworks seems to be very representative of the underlying language's philosophy, so I bet it mostly boils down to which or Ruby or Python fits your brain best. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
