Cutting Through the Ajax Hype
An anonymous reader writes "If you're thinking about building an Ajax application of your own, this article would be a good place to start. It's an introductory-level guide about when and how to implement Ajax. It provides a balanced discussion about where exactly using Ajax makes sense, and where it does not."
Now that Google has released GWT as open source. All the fanbois will rush to ajaxify their sites regardless of requirements, creating even greater mostrocities while all the time laughing at sites which are not sufficiently 'ajaxy'.
Then XAML and XUL will see greater adoption for rich client development and we return to the days when ajax was just a household cleaner.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
The thing that made AJAX catch on is that a few of the very first notable web apps were very heavy on graphic design and well-thought-out layout.
So now everybody thinks that if their website can just be written with AJAX technology it will automatically come with a smooth, user-friendly and beautiful interface.
AJAX is just one technique. You still need to be highly skilled at all the other web-coding disciplines else to end up with a great web app.
Plug-ins are often "shoved aside" so that the application will run in some of the strict corporate IT environments. A bunch of our customers (mostly banks) don't allow any plug-ins installed on their users' machines. We'd love to use flash instead of AJAX, but we're forced to use only features of the core browser.
No - you couldn't find your address because you were stupid enough not to jot it down on a piece of paper when you had the chance. Seriously, blaming GMail for not being able to access data locally is asking a bit too much of the Internet, le talone of Ajax!