Hmmm, I see where you are coming form, but my comments were more geared towards
where we should focus our efforts. As you said we will continue working on
performance. However I think we should give UI performance higher priority then
just rendering generic xyz page.
I agree a criteria should not say UI elements should X fast.
However I don't see anything wrong with saying UI in general should be faster for
1.0.
Gervase Markham wrote:
> > Over all page rendering is good, but our UI still is sluggish on slow machines
> > or machines with many other apps running. I would encourage our focus of
> > Performance to be in areas that help the over all UI. naturally the why
> > mozilla works helping the UI may also help other areas also.
> >
> > Memory usage and memory leaks are also still a problem that needs to be
> > addressed. I know from reading .porkjockies that it is something that is
> > being worked on. Again that should be an area of focus for our Footprint
> > Performance and Stability people.
>
> I don't deny that these things will continue to be worked on; but that's a
> very different thing to saying "We require measure X of performance and
> amount Y of stability by 1.0". We could say that MTBF has to be, say, 200
> hours - but we'd just be pulling numbers out of the air.
>
> We will continue to work in these areas; however, "Mozilla should not be
> sluggish on slow machines" is not a very good 1.0 criterion.
>
> Gerv
