In light of how ajax is actually used by most sites today; why is ajax embraced while frames are still regarded as a bad idea?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In light of how ajax is actually used by most sites today; why is ajax embraced while frames are still regarded as a bad idea?
AJAX, from where I’m sitting, is a sort of grand tradeoff. You are breaking things in the ‘document’ model of the interwebs so that your site can behave more like an ‘application.’ If a site is using AJAx well, they will break the document model in subtle ways that add something of value to the application. The ‘vote’ link isn’t really a link, but it gives you a cool animation and updates the question’s status asynchronously.
Frames break just as much, if not more, of the document model (bookmarks, scrolling, copy-and-paste, etc) but without as much of the benefit. Frames also insert whatever decorations my OS/Window manager happens to be using, so they look pretty ugly.
AJAX, if done correctly, also breaks better for people using screen readers, text-based browsers, etc.