[Pewpewarrows]

So let me get this straight. You didn't like Django because after not taking the time to learn it, you couldn't get it to do what you wanted. So you switched to a very lightweight model (webapp2), and loved the learning curve and flexibility. And then you tried out Rails (about as Django as you can get in terms of steep learning curve and having to contort to do non-traditional things) and loved it.

Nothing in that logic adds up. And for the record, I've yet to do a "traditional" web app in Django. Having taken the time to learn it inside and out I get all the benefits of flexibility that I would with something like Flask/webapp2, but retain the convention and mindshare for the rest of the project that does fit into common usecases.

[josephmosby]

As I stated in an earlier comment, I would likely have a different experience with Django now. Django was the first framework I attempted to learn, so I'll wholeheartedly admit that some of that was inexperience with web applications (started programming with non-web VB and Java).

I could write much of the same post and have it apply to Django as well. Django is designed to abstract away work, which means that it's difficult to really see what your application should be doing if you don't already know. If you've learned how to manage user authentication manually, you can appreciate and tweak what Django/Rails are doing. If your first experience with a web framework is having Django manage all of that for you, then you have no idea how to tweak it or debug it.

Ultimately, this is not a Django versus Rails debate - I just used my current Rails experience and prior Django experience as anecdote. I can't claim enough knowledge of Django or Rails to even advise someone on which to learn; all I can do is talk about my own experience and raise questions.