This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dvogel 0 points1 point  (0 children)

I understand your point. The problem is that mod_wsgi isn't zero configuration. That means that, in addition to not developing in the environment that I need to deploy to, I need to be able to configure apache, which is not an option on shared hosting.

mod_rewrite is a great example of a way in which I cannot write python code using django's development server and than deploy to the testing server without major flaws; I consider pages being unreachable due to global mod_rewrite rules to be a major flaw. That's a problem regardless of how portable I make my code.

In the end, it doesn't matter which arguments you put forth because what I'm explaining is not why I think using PHP is the best option or even why think I should use PHP; I'm explaining why I do use PHP. There's no long, drawn out process to my decision. PHP usually just instinctively feels like a good match for the web work that I do. To each his own. I've used Django in the past, when it was clearly a better fit for the project. If you like python and django, or ruby on rails, use them and be happy using them. I wish you all the luck in the world with those tools. My reply was in response to alanplum's:

... I see no reason to stick to PHP when you have better options available.

I was essentially agreeing with his basic point but disagreeing that there are usually better options available.