How we seamlessly moved from PHP to Django over 22 months

There are two things that strike me as odd in this report:<p>1) Why would you go through the process of switching the language. There are perfectly suitable frameworks in PHP, e.g. Symfony, that have the exact same approaches than Django and ROR. MVC, ORM and configuration over Convention over Configuration. Once you have a team that is good at a Language, you'll loose a lot in switching... and this leads me to the second question:<p>2) How can it take 22 month to rewrite this kind of application? A bit of CRUD and workflow should not take so much time.<p>WDYT?

On the one hand, kudos to a team for taking on a big project and getting it done without interrupting service. But on the other, the article does nothing to explain the why-behind-the-why. Why did this change need to happen? What benefits are they now realizing? What aspects of Django attracted them in the first place? I want the sequel to this post.

That is very much a good way to do it. However for 22 months, I was expecting a larger project than one with 45 php files.

What is the performance difference (page load, processor load, memory load) after switching?

Nice hack on the session sharing. "2. Build a Django Session Engine using phpserialize to speak PHP's serialization format"

I would very much like to see his Apache vhost.conf file!