2 ms·
1. Really? Compared to throwing a few pages out with PHP but on complex apps the time you save not reinventing the wheel would be the payback. 2. Hard to know
by andybak 17y ago
1. Really? Compared to throwing a few pages out with PHP but on complex apps the time you save not reinventing the wheel would be the payback.
2. Hard to know what you were doing wrong without more info.
3. I've found excellent Django coders for less than $15 dollars/hour through freelancer sites.
4. The conventions around reusable code are growing up as the Django ecosystem grows up. There are good and bad examples but it's very possible to write reusable apps if you use the right architecture and separation of concerns.
5. Again. You are doing something wrong.
6. Django does use more memory than a simple mod_php setup and Pinax is a complex project but I'd like to see numbers once you compare apples to apples. ie. PHP+framework as a long running process matching Pinax for functionality. Would the memory requirements be that different?
7. Sounds like it's your server technology that's giving you those errors. You'd have to tell us what the underlying Python errors were for us to know whether Django was at fault or your setup.
8. You are not alone in thinking this but that is viewed as a feature for people trying to run stable sites. If you want to live on the bleeding edge then join the django-experimental branch that has opened recently on Github
9. Huh? Most people complain the Django template system is too simple and therefore limited.
10. I have no idea what you are trying to say here.
You do sound slightly trollish. Give us a bit more info to go on and we can have a constructive debate.