I'm a bit of a noob as well, and know nothing about Rails, but I'd like to comment on a few issues you mentioned.
1. Non-existent template variables are replaced with the value of the TEMPLATE_STRING_IF_INVALID setting. Set that to something besides its default (an empty string) to make non-existent variables easier to find. 2. Regarding documentation, the docs at http://docs.djangoproject.com are, in my opinion, simply amazing. By far the best documentation for a free project that I've seen (but then again, I haven't seen much). And that's just a matter of opinion I guess =) 3.I have yet to encounter any problem with the dev server, although I remember issues like that from App Engine. Irritating as hell. 4. I find the error handling in Django (basically just Python error handling) works quite well. I sometimes get rather ambiguous errors, but their solutions become easier to find as you encounter them. One error I always hated with PHP was when you forgot to put a semicolon on the end of a line. PHP said the first thing on the _next_ line was unexpected. It seems ambiguous at first, but after you see it a few times, you know exactly what it means. Same with Python/Django. That's all I have to say. Hope I helped. =) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
