Is Rails much better for interactive website compare to Django?
Question: Just got a new website project for my company internal use. The whole website
isn't that complicating but requires quite a lot of real time interaction.
Basically, it's an interactive time line table where we can freely drag and
drop each elements to move and resize them.

At first I wanted to use this opportunity to learn Python+Django (I'm given a
huge amount of time) but then I read around and a lot of people mentioned
Rails is better for creating rich interactive website.

So, for a website with a lot of drag & drop interaction like this, is Rails
really the better choice? Is Rails built-in ajax that much easier to work with
compare to Django+jQuery? How flexible and customizable is Rails' built-in
ajax? I want to learn RoR just as much as Python by thee way.


Answer: I don't think AJAX functionality will define which framework you find yourself
preferring.

I can't answer most of your question relating to ajax, but still think this
post could be useful for you: it's highlighting a huge difference between ROR
and django -- mainly RoR uses magic, django doesn't.

I prefer django for exactly that. Others may prefer RoR for the same reason I
don't.

[What's wrong with "magic"?](http://stackoverflow.com/questions/441717/whats-
wrong-with-magic/442088#442088)

> Rails' developers are of the opinion that this sort of "magic" is a good
> thing because it makes it easier to quickly get something working, and
> doesn't bore you with lots of details unless you want to reach in and start
> overriding things.
>
> Django's developers are of the opinion that this sort of "magic" is a bad
> thing because doesn't really save all that much time (a few import
> statements isn't a big deal in the grand scheme of things), and has the
> effect of hiding what's really going on, making it harder to work out how to
> override stuff, or harder to debug if something goes wrong.
>
> Both of these are, of course, valid stances to take, and generally it seems
> that people just naturally gravitate to one or the other; those who like the
> "magic" congregate around Rails or frameworks which try to emulate it, those
> who don't congregate around Django or frameworks which try to emulate it
> (and, in a broader sense, these stances are somewhat stereotypical of Ruby
> and Python developers; Ruby developers tend to like doing things one way,
> Python developers tend to like doing things another way).

So I think one will click for you regardless of out of the box ajax support.

