On 11/14/05, Simon Willison <[EMAIL PROTECTED]> wrote: > For me "Ajax support" really is pure marketing fluff - as far as I'm > concerned EVERY web framework supports Ajax unless it does something > truly moronic like refuse to let you output documents that don't have > the standard header/footer template.
At the point of a developer deciding, it's *ALL* about marketing. You have about 2-3 clicks for him to decide if the framework is worth looking further into. Some developers think ajax is hot stuff, and it will make their app look sexy in front of their PHB, so they want it supported out of the box. Others think it is a waste of space, and they can do the job better by rolling their own. this is the real 'marketing' question here.. Who do you want to use django? If you want django to be popular and in wide use you will need to add ajax support for those who want it. The 'trick' i guess is how do you design the framework so it can have ajax support, and the ability to turn it off. regards Ian -- [EMAIL PROTECTED] -- ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti
