Mike took out that preference because it's not doing Camino any good if you look at startup performance. People with a ton of bookmarks will have startup times above 10 seconds and camino turning unresponsive which is just ridiculous. We (I agree with this with Mike) shouldn't put in eye-candy features that push down our basic performance.

We would love the favicons to be available always, bit for the moment there is no real good code that doesn't touch our performance. This or any other application should never let it's user wait for non trivial things like favicons.

But that's just my opinion.

As to why Camino development is so "flexible", remember that this application is still a MAJOR PRE 1.0 VERSION. When code is checked in things are tested and then things are changed again and again and again until it's right. That's where most of you guys get in the story, you use it and tell us what sucks and what kicks ass. So things will get changed along the path.

Don't forget that most of the discussions that are made are done for common benefit. So if you have a VERY GOOD REASON for something to be put back or be changed I'm sure we will listen and eventually change something.

—:0-0:— jasperhauser.nl

_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino

Reply via email to