On Sun, Dec 7, 2008 at 7:39 AM, Ben Bangert <[EMAIL PROTECTED]> wrote:
> On Dec 6, 2008, at 9:31 AM, zunzun wrote: > > Comparison before starting a project, used to decide which framework >> to use. >> Django: according to http://groups.google.com/group/django-users/about >> Members 12,016 >> Group Activity is High >> Pylons: according to http://groups.google.com/group/pylons-discuss/about >> Members: 1,748 >> Group Activity is Low >> > > Really? That's how you decide? Then I believe you *must* choose PHP. It > completely dwarfs Django and Python altogether, its the only choice really > if you want to determine framework based on user-base (popularity). :) > > Also, Django just made a major release. The last (non-security fix) >> Pylons release is over a year old. Guido van Rossum has blessed >> Django here: >> http://www.djangoproject.com/weblog/2006/aug/07/guidointerview/ >> > > Before that release, they hadn't made a release in almost 2 years, and > actually told everyone to run production websites on the development > branch... Pylons 0.9.7 RC4 came out about 2 weeks ago. Guido is not a > veteran web developer, nor does he actually use any of Django beyond Django > templates, his apps have been generally built with pure WSGI and Django > templates, the recent port of his Mondrian to a Django app was prolly his > first actual Django project. > > Seems like I should use Django? Or should it be Pylons instead? Is a >> long-planned major release immediately forthcoming? >> > > What kind of app/site are you building? What tools matter to you? Do you > think you'll need to scale heavily? Are you talking to a legacy database? > etc. > > Those questions are the ones you should be asking yourself, then seeing > which framework has the tools you need to accomplish your task. Otherwise, > merely posting some mail list numbers and that Guido likes Django seems to > be awfully trollish as it doesn't seem to be a serious attempt to evaluate > the frameworks benefits for the task you're actually trying to complete. > > I'd highly suggest searching the mail list for some previous threads on the > subject, as this doesn't really need rehashing again. > http://markmail.org/search/?q=list%3Apylons+django+pylons I wouldn't necessarily agree that it doesn't need rehashing, at least from a marketing and documentation perspective. I just talked with some co-workers last week, that are very experienced Python programmers and they asked me why they hadn't heard about Pylon's much. One person mentioned he looked at it about a year and half ago, and decided to go with Django. Now he ran into a problem that only SQLAlchemy can solve, and after he went through the new pylons book online he was quite impressed. In my opinion Pylons and Django solve two different problems, although there is some overlap, but even still many people don't know this. For example, if you have several legacy databases that you need to talk from the same web application, while you are dealing with parallel processing farms, then Django is going to cause you much, much pain...i.e. the typical film animation workflow. If you want to write a CMS from scratch, Django is damn nice. To be fair I do agree too that Pylons has had some documentation, installation, marketing issues, which I have whined about as well :) It sounds like a lot of this is resolved with the book, new installation procedures, and people writing articles and blog posts about Pylons. I think looking at the Ruby framework Merb is a good comparison to see how successful, and viable multiple framework approaches are in a language. Not every problem for Ruby is solved by Ruby on Rails. Many people are unhappy with parts of it, and Merb seems to address this. <http://markmail.org/search/?q=list%3Apylons+django+pylons> > > Cheers, > Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
