For the most part, your average website is a slideshow in a sense, static sites in which visiting separate pages require a momentary "loss" of the interface/design after the click.
Ajax/js helps rid this problem. I'm no "pro" when it comes to coding, and especially not ajax/js, in fact I just started learning it the other week by building a site: FrenchCry.com | Let it out - The login, the register, the posting, basically everything about it is 100% ajax/js and there are no page reloads.
As far as the "user experience" is concerned, while trying not to be biased, it seems most ideal when you don't have to wait for an entire page to reload and have the design disappear for a brief second..
Of course there are issues that are probably hindering the prevalence of full ajax sites. One being an excessively large *initial* page load if it's a big site with a lot of JS. Two being a useless back-button, though if the site is designed/structered well enough, that might not be such an issue.
Anyhow, thoughts? Just some food for thought, bored waiting for food to cook.
Ajax/js helps rid this problem. I'm no "pro" when it comes to coding, and especially not ajax/js, in fact I just started learning it the other week by building a site: FrenchCry.com | Let it out - The login, the register, the posting, basically everything about it is 100% ajax/js and there are no page reloads.
As far as the "user experience" is concerned, while trying not to be biased, it seems most ideal when you don't have to wait for an entire page to reload and have the design disappear for a brief second..
Of course there are issues that are probably hindering the prevalence of full ajax sites. One being an excessively large *initial* page load if it's a big site with a lot of JS. Two being a useless back-button, though if the site is designed/structered well enough, that might not be such an issue.
Anyhow, thoughts? Just some food for thought, bored waiting for food to cook.