Wilson wrote: > So far the discussion of "AJAX support" in Django has been a relatively > contentious one. There seem to be two viewpoints at the heart of this > conflict, which are not mutually exclusive in their substance. At the > risk of being unfair, let me grossly generalize the two positions. > > 1. AJAX is the future, and Django should be on board. AJAX may be > overhyped, but it's hyped for a reason. AJAX is a core component of > developing modern Web apps, and as a modern web framework Django should > support AJAX as a core feature. > > 2. Django already has all the AJAX support it needs.''' As a backend > framework, Django needs to provide data in a standard way that's easily > consumable by any AJAX toolkit (following the rule of loose coupling). > Since choosing wizzy frameworks is becoming a web development holy war, > Django should support any of them. > Not to fan the flames, but I think my position has been a bit distinct from these:
3. There are requirements for the bundled apps to make use of extensive JS functionality. If we don't bundle an existing toolkit, we will end up inventing a new one, or selling the bundled apps short. Not making a decision does entail a cost.