title: What are the real world differences between Zend Framework and Django?
body: <p>I am a long time PHP user when it comes to web applications and am mostlz comfortable with it. However, I have a one semi-large project whose maintenance / extensibility has reached its end of a life cycle. I was weighing on different PHP frameworks (there were no when the project originated), since it is the way to go for this project, and I came to conclusion the ebst option would be to do it with Zend Framework.</p>
  <ul>
  <li>Symfony seemed to complicated (I don't like setting up database model as that</li>
  <li>CakePHP seemed murky</li>
  <li>Igniter I liked at first, but then it seemed to me it is more like Zend with less features and no Zend behind it</li>
  <li>Zend I like the system of that I can use only what I like and not being tied into a specific directory structure, and of course there is Zend behind it. Performance is what potentially bothers me</li>
  </ul>
  <p>Now, after this little rationale behind choosing Zend, there are several things I see as a deal breaker when choosing a framework.</p>
  <ul>
  <li>I haven't used ORM in the past because I am more than comfortable writing SQL directly, so I still need to be convinced to use ORM</li>
  <li>Not too much abstraction going on from the guts</li>
  <li>Flexible directory structure</li>
  </ul>
  <p>
  As long as this project is going to be written anew, I just as might write it in Python/Django, since I am quite familiar with Python, but not with Django. So, I would like to know if there is someone that worked with both Zend Framework and Django frameworks and if can outline a few key point differences?
  </p>
  <p>
  I must also say that this project is made as a standard site/admin dual project. That is, it is basically two sites in one. One is for frontend and users, other is for data administration in the backend. I must and will build backend on my own, some scaffolding methods would be cool, but full automatic scaffolding is as good as nothing in this case.
  </p>
  <p>
   I am still quite not sure how one approaches building basically two applications within a directory structure of, what is supposed to be, one application. Do you just make two separate applications and rely on URL scheme from there on to separate them? www.example.com and all of the /* being one application and www.example.com/admin/* being a second application.
  </p>
  <p> 
  Sorry for the long question(s), but as you can see - everything is pretty much related to one problem - I need to start a project anew, it has already established database+data which I can remodel, but would like to keep that kind of work at minimum.
  </p>
  <hr>
  <p>
  Ok, thank you everybody - looks like I'll try and implement this stuff with Zend, gives me most flexibility out of the package (I did tests with both), and we'll see how it goes.
  </p>