Linked by Thom Holwerda on Fri 25th Nov 2005 15:50 UTC, submitted by Francis
Thread beginning with comment 64565
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Federico Mena-Quintero
by Beryllium on Fri 25th Nov 2005 17:16
in reply to "RE[2]: Federico Mena-Quintero"
Member since:2005-07-08
RE[3]: Federico Mena-Quintero
by on Fri 25th Nov 2005 17:24
in reply to "RE[2]: Federico Mena-Quintero"
Member since:
There's on old addage: Early optimization is the devil; or something along those lines.
It's "early optimization is the root of all evil."
It's because 90% of your programs time will probably be spent in 1% of your code..
It's 90% in 10%, not 90% in 1% 
Obviously, though, it's the general idea that matters.
-bytecoder
RE[4]: Federico Mena-Quintero
by ma_d on Sat 26th Nov 2005 01:34
in reply to "RE[3]: Federico Mena-Quintero"
Member since:2005-06-29
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-06-29
Most of these folks have day-jobs; maybe you should just avoid software in general
.
Very little slow code will cause a noticeable loss in speed. There's on old addage: Early optimization is the devil; or something along those lines. It's because 90% of your programs time will probably be spent in 1% of your code..
It does surprise me that firefox stores all of these as pixmaps on the x server. My guess is that is in fact for performance... I'd imagine the people who worked on that said "well, RAM is cheaper than clock cycles." What they need to do, IMO, is set a max X server memory usage so that you can view pages with 50MB of jpegs without swapping (cause swapping is slower than decompressing). Say, 100MB of X memory, and then get smart about what you don't store on the X server: That's a lot more work, but I think it's worth it for a lot of users.