Re: Chrome is a resource hogging abomination
Yes and no.
Chrome is a resource hogging abomination on a terminal server (regardless of the terminal protocol). The reason for this (and one of the reasons for its perceived "fastness" on normal hardware) is that it does most of the rendering on a canvas internally and updates the whole canvas at a time. Compared to that Firefox uses much more graphic prmitives from the underlying graphic subsystem. This allows remote access protocol implementations to optimize redraw and do a lot of ops locally. They do not get that chance with Chrome.
As a result of this, Chrome when compared to Firefox (or MSFT offering for Windows T Server) sucks royally in a thin client environment.