A Few More Thoughts on Django & Pylons

• Curiously, one of the effects of the wide readership that the post got was heightened interest in my django based package: django-gitcms.

  This is good. I still plan to put up a couple of websites based on that having spent a few hours two weeks ago making it more general (even as I was switching to Pylons for the other project).

• Some people pointed out that my criticisms were about the apps and not the full architecture. For example, someone said doing a photo app that handles twitter is easy with signals. RTFM.
  It’s actually a good idea. The only question is: where is that app?

  I think it’s fair to evaluate a platform based on the tools that are built around it as much as on the full potential. Django has a bit of a culture of releasing any piece of half-finished code that served its purpose once as an app.

• Let me reformulate a bit of the gist of what I wrote: Part of the django vs. Pylons trade-off as I understood it when I first chose django and still understand it now is that django constrains your website more, but gives you more for free, while Pylons is more build-your-own, but you have a lot more flexibility. When I realised that I was mostly building my own with django while still being constrained, I felt that I had been cheated on.

  Other websites might not like the flexibility or not mind the constraints. Fine.

• We should all unite against the common enemy: Ruby on Rails! I hear. No, PHP. Oh, yeah, PHP.

Follow me on twitter: @luispedrocoelho