FJAX vs AJAX vs plain page

Recently I came across this page FJAX, and this is what it does….

• Make HTTP calls
• Get and parse XML
• Render stuff

You’d say how different is it from AJAX, Well only in a way it uses a stupid Flash file which does all that.

Well AJAX does the same, but it still does not use any other plugin. Now why on earth a developer would use such a library where he has an added restraint of the browser having a specific plugin (Flash in this case)

People nowdays are getting over the wire with this AJAX thing. No doubt its helping change the format of the Web-based Application, which is turning into a more fancy, jazzy desktop like app. But still we must understand it is HTTP, however you try to build, still it has same limitations that of HTTP.

Consider this screenshot of FJAX.net,

Look at the loading page…, this all loading is just to grab another XML file that has contents, that is to be displayed for the indexpage. So what these new “AJAX geeks” are doing are making 2-3 more calls for every page, as compared to a plain HTTP page, which would have simply fetched the main page (with its attached images… etc.) and displayed it…

In the application above,

1. Load the main page (with attached images, files)
2. Load all the heavy Javascripts…
3. Load the XML file, that shall deliver the contents
4. Javascript shall now render the XML-content.

Instead for a plain HTTP page.

1. Load the main page (with attached images, files)

… thats it.

Luckily I’ve got someone to support my idea, FJAX: Just say no