Django -vs- Grails -vs-?
The statement that grails deletes the database on start-up is completely wrong.  It's behavior on start-up is completely configurable and easy to configure.  I generally use create-drop when running an app in dev mode.  I use update when I run in test and production.
I also love the bootstrap processing that lets me pre-configure test users, data, etc by environment in Grails.  
I'd love to see someone who has really built and deployed some commercial projects comment on the pros / cons.  Be a really interesting read.
I'm wondering if there's such a thing as Django-like ease of web app development combined with good deployment, debugging and other tools? 
Django is a very productive framework for building content-heavy sites; the best I've tried and a breath of fresh air compared to some of the Java monstrosities out there. However it's written in Python which means there's little real support in the way of deployment/packaging, debugging, profilers and other tools that make building and maintaining applications much easier. 
Ruby has similar issues and although I do like Ruby much better than I like Python, I get the impression that Rails is roughly in the same boat at Django when it comes to managing/supporting the app. 
Has anyone here tried both Django and Grails (or other web frameworks) for non-trivial projects? How did they compare?