11👍
Ajax and reporting and Django go quite well together, so if you find yourself more comfortable at Python (no surprise there) and would like a well rounded framework to code in – Django is the way to go. It does not get in your way while being pretty full-featured, we have production Ajax sites with heavy reporting (all custom though) and never regretted going with Django over RoR or especially PHP.
19👍
We use PHP + Cake. Absolutely avoid Cake. They have painted themselves into a corner by insisting on PHP 4 compatibility. The ad-hoc growth of PHP has made it a bit of a Franken-language. I yearn to use python on a daily basis instead of PHP. This is just a personal opinion, but I encourage you to go the python route.
The PHP documentation is sufficient, but excessive. The user-contributed notes create the impression of bulk, but they are often inconsistent. The official documentation is sometimes lacking, and it merges the PHP versions together. By comparison, the python documentation is thoughtful, well organized, and separated by version.
- [Django]-Request.user returns a SimpleLazyObject, how do I "wake" it?
- [Django]-How to limit django admin inline formsets
- [Django]-What is the equivalent of django.db.models.loading.get_model() in Django 1.9?