Wow, I can't even begin to tell you how misinformed you are.
Rails is not geared towards web apps, and Django is not geared towards web sites. Both tools are what you make of them; just because Django includes a built-in admin interface doesn't mean it has to be "rejiggered" to build anything else. Both, as full-stack frameworks, provide nearly exactly the same set of tools to the developer: an ORM, a templating language, a routing framework, and the glue that ties everything together.
You are also patently wrong about the importance differences being at a higher level. If you are only using the shallow, superficial features available to you, you are missing out on the differences that do make each framework unique. Anyone who has spent any quality time with either framework can tell you that these "high level" features (e.g. Rails scaffolding or Django's Admin) are almost never used in a real project. Next time, I would highly recommend going beyond the 15-minute screencast and actually reading into the guts of your framework. Who knows, maybe you could become a professional one day ;).
You speak with such authority, evdawg, I find myself wondering which of your many Django and Rails projects I must use every day without even knowing it. Care to tip us off?
Interesting rant about being misinformed, considering the assumptions you make about both my experience with the frameworks as well as my "professional" working experience. How about the fact that I've worked exclusively at two different Django startups over the last year and a half? And with several Rails startups in the 4 months that I've gone freelance since then?
Rails is not geared towards web apps, and Django is not geared towards web sites. Both tools are what you make of them; just because Django includes a built-in admin interface doesn't mean it has to be "rejiggered" to build anything else. Both, as full-stack frameworks, provide nearly exactly the same set of tools to the developer: an ORM, a templating language, a routing framework, and the glue that ties everything together.
You are also patently wrong about the importance differences being at a higher level. If you are only using the shallow, superficial features available to you, you are missing out on the differences that do make each framework unique. Anyone who has spent any quality time with either framework can tell you that these "high level" features (e.g. Rails scaffolding or Django's Admin) are almost never used in a real project. Next time, I would highly recommend going beyond the 15-minute screencast and actually reading into the guts of your framework. Who knows, maybe you could become a professional one day ;).