On Jul 16, 2009, at 10:09 AM, Tom Longson (nym) wrote: > I think the relative number of django apps in the wild vs pylons apps > is a good indicator of how "easy" it is to get something launched. Not > that I don't <3 pylons, but django's developer base speaks for itself.
Django's massive code-base and monolithic nature *require* its larger developer base. Pylons doesn't have such a developer base, because it doesn't *need* one as its code-base is tiny in comparison, and divided into clean and separate components that can be easily updated and released independently of one another. So far, in the Pylons 1.0 branch, removing the legacy support dropped another 400 lines of code to bring Pylons in at *under* 1000 LoC. Anyways, I believe this thread is about Pylons use in the read world. Let's keep on topic, there's more than enough debates elsewhere on the topic of Django vs Pylons. > Either that, or pylons needs a marketing campaign with a pony or > something. Thankfully we have no pink ponies. :) 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
