4 ms·

Is anyone surprised that Pylons doesn't get enough credit. I prefer it to Django for most projects.

• dood 19y ago
  I suspect its because Pylons has only relatively recently reached a stage where the code and documentation makes it simple enough to dive in and do great things without too much hassle. I think Pylons has broader and deeper goals, so there has been a period of ramping up and getting the foundations in place, while the efforts put into Django's development have been focused on making specific things easy. Now Pylons is settling down and maturing, it will probably start to become much more widely used and appreciated. Also, Pylons may benefit from Django's recent boost in a similar way the link suggests Django is benefiting from Rails.
• hbien 19y ago
  How do you like it better than Django? I've been wanting to try it out for some time now but haven't found the time. Sometimes I think the included apps in Django too heavyweight. I get a lot of "just because it's included doesn't mean you have to use it" and "don't re-invent the wheel"/NIH responses from the mailing list.
  • simonw 19y ago
    "Just because it's included doesn't mean you have to use it" sounds like a pretty good argument to me. The Python standard library has hundreds of modules that most people never touch, but no one complains that it's too heavyweight. Django tries to take the same "batteries included" philosophy.