Comments on: A Study of Ajax Performance Issues

By: Aphrodisiac

Aphrodisiac — Fri, 15 Aug 2008 10:41:23 +0000

Yes “all major browsers” but not including Safari or Opera is misleading.

By: olliej

olliej — Wed, 30 Jan 2008 11:12:39 +0000

Ah ingore the first point — i see that the original article does at least cover safari — although the absence of opera is somewhat poor.

By: olliej

olliej — Wed, 30 Jan 2008 11:09:09 +0000

Two points: referring to “all major browsers” but not including Safari or Opera seems to be misleading.

The second point: getElementsByTagName does *not* return an Array it returns a NodeList. The difference? NodeList is a dynamically updated list that always reflect the current state of the dom — or at least it should, i’m not sure what the JS implementations do.

By: Les

Les — Mon, 28 Jan 2008 15:18:37 +0000

>> FireFox needs to improve performance of â€œevalâ€
eval is much faster in FF 3

By: Mark Arrington

Mark Arrington — Mon, 28 Jan 2008 14:58:24 +0000

Ajax is becoming the word that represents general DHTML programming these days. So calling it “Ajax performance” is fine.

By: Maxim Kozhukh

Maxim Kozhukh — Mon, 28 Jan 2008 14:03:36 +0000

>>Why isnâ€™t Opera included in this little Test? The similar list with addition of Opera and the list for oncoming versions of browsers

By: Dov Katz

Dov Katz — Mon, 28 Jan 2008 12:26:18 +0000

While it’s very interesting to see how browsers natively perform, I’d be even more interested in seeing how AJAX Libraries such Prototype and JQuery possibly help us get better performance through their convenience methods for DOM manipulation and accessing. I don’t do as much native browser-level DOM manipulation as I now often leverage the libraries for this.

Perhaps someone representing the libraries can take this existing table/grid and add their convenience methods and metrics for comparative purposes, and comment on how they may help people avoid the cross-browser performance pitfalls?

By: Zsolt

Zsolt — Mon, 28 Jan 2008 12:17:21 +0000

Why isn’t Opera included in this little Test? Because it was to fast to be measured?

By: Ronni Rasmussen

Ronni Rasmussen — Mon, 28 Jan 2008 11:51:25 +0000

By itself it dosnt have anything to do with Ajax but these operations results is based on methods often used after reciving ajax request response. So i guess the title can be accepted now its about the Ajax performance issued.

By: Daniel

Daniel — Mon, 28 Jan 2008 11:24:25 +0000

Haha, indeed

By: SchizoDuckie

SchizoDuckie — Mon, 28 Jan 2008 10:59:34 +0000

Why does the word Ajax have to be in here?

It all comes down to Javascript doesn’t it?