there are totally unfair comments to django, django committers and the django users. having used many tools such as grails, rails, django, pylons, turbogears an

there are totally unfair comments to django, django committers and the django users. having used many tools such as grails, rails, django, pylons, turbogears and pyramid for different size of projects and loving them all i have a good amount of experience with these tools. whenever i needed a hand, people in #django (in irc.freenode.net) or a djangonaut's blog post or answer on stackoverflow or the django mailing list helped me out. same applies to rails as well. what you like with rails is its just being fancy and people acting like it's a miracle. it's not. it's a a tool which helps you prototype your application with scaffolding and some other nice things in a very small amount of time. so is django. complex application means complex code. this is not a django thing. it applies to every tool. do not let screencasts or posts hypnotize you as those guys are working with rails for many years. you will not develop rails apps like they do when you start over. your code will suck. you won't like your own code as you learn ruby and rails in depth and sharpen your skills. oh wait, that applies to python and django as well. :) it's not you though, we all have been there. one final note. django community does not need a reference book. because django documentation is a reference manual that contains everything a django developer needs. however a cookbook or application-type teaching book would be nice.