Re: Selector for parent/predecessor?

Mark Birbeck wrote:

> In most languages an author is aware of which operations are costly,
> and which not, and can then make their own decisions. For example,

This must be an enormous joke...
The Web is so pure, so clean, people know so well how use selectors
effectively, write cost-effective javascript or flash that does not
freeze the visitor's machine.
And all c and c++ programmers are algorightm experts.

Oh, and XSLT does not exist, of course.

</Daniel>