I started my current project in Grails, and switched back to Rails, because debugging was a nightmare. Massive stack traces (multiple hundreds of lines) due to

I started my current project in Grails, and switched back to Rails, because debugging was a nightmare. Massive stack traces (multiple hundreds of lines) due to reflection, and some really irritating typecasting nightmares due to the String/GString difference. The long-running memory leaks were the sort of things the Vikings wrote poetry about, because even Beowulf couldn't smite them. Not to mention some massive showstopper bugs in Grails, things like 'logging doesn't work, and yes, we know.' Also, if you want to 'break out of the box' in Grails, and are not a really seasoned Spring/Hibernate developer, good luck. Groovy is a nifty language, and I like the idea of Grails. It's a great tool if you're already an experienced Java/Spring/Hibernate developer, but it isn't really a Rails replacement.