The "iGoogle bug"

[Jim Gettys]

Ah, X's guilt is no more (in this instance): at the time you wrote that
amusing tirade, there was no way to find out the memory consumption in
the X server due to stupid clients: now there is (XRes)....  

Would that more tools used it to report memory properly....
			- Jim


On Tue, 2007-09-18 at 10:45 +0200, Don Hopkins wrote:
> > This is #3352: https://dev.laptop.org/ticket/3352
> >
> > What's special about this page is that the clock applet uses two
> > very wide bitmaps of 3200 pixels each to represent the clock arms in all
> > possible positions.  (that's over 2MB of RAM wasted, nice!)
> >   
> 
> Wow, 2MB of ram for a clock? That's 32 Commodore 64's: even worse than 
> Sun's Open Look clock tool! Kids these days...
> 
>  From the "X-Windows Disaster":
> http://www.art.net/~hopkins/Don/unix-haters/x-windows/disaster.html
> 
> "X has had its share of $5,000 toilet seats -- like Sun's Open Look 
> clock tool, which gobbles up 1.4 megabytes of real memory! If you 
> sacrificed all the RAM from 22 Commodore 64s to clock tool, it still 
> wouldn't have enough to tell you the time. Even the vanilla X11R4 
> "xclock" utility consumed 656K to run. And X's memory usage is increasing."
> 
>     -Don
> 
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys
One Laptop Per Child