News for hackers. Stuff that matters.
Re:Ask HN: Bet the farm. Python or PHP? by wensing on Saturday June 07, 2008 @10:07PM (#211843)
you don't run Django, it runs you

I use Django (GeoDjango actually) at my full-time job, and love it. My progression was PHP -> Python -> TurboGears -> Pylons -> Django. I can say with confidence that it is the best of them all. Yes, many choices have been made for you, but they have been made in an elegant, Pythonic way, and you retain the ability to get under the hood to a healthy extent.

Re:Ask HN: Bet the farm. Python or PHP? by mrtron on Sunday June 08, 2008 @01:29AM (#211950)
I have used Django at a well known web company and then at a startup and many other projects.

Django is fantastic, and 'it runs you' would only hold true if you used the basic features and built in admin system and nothing else.

Re:Ask HN: Bet the farm. Python or PHP? by noahlt on Sunday June 08, 2008 @12:09AM (#211903)
May I ask why you switched from Pylons to Django?
Re:Ask HN: Bet the farm. Python or PHP? by wensing on Sunday June 08, 2008 @10:50PM (#212468)
The real reason I switched was because I began working at a newspaper, and Django and journalism are married/fused inextricably. Choosing Pylons over Django in a news endeavor would be rather ... odd.

That aside, I said I progressed from Pylons to Django because I would choose Django if I had to do the Pylons project over again. Why? Because although I rejected (rebelled against?) it at the time, being 'forced' into an ORM for data entities would have been a really good thing. Since Pylons "lets" you shirk an ORM, I did ... but the result feels more like PHP than Python. Turns out Django's hand-holding is, in many cases, good because the answer they provide is the smart thing to do. And doesn't that sound like a description of Python itself?

Would I choose an ORM-ified Pylons experience over Django? Probably not. Django routing seems better, there's Django-enhanced unit testing, and I even prefer the way Django forces you to keep Python out of your templates in favor of "template tags" and "filters".

Perhaps most importantly, Django has nearly-impeccable documentation, and a thriving community.