3 ms·
How about fixing the memory leaks before revamping the UI? the ui is fine.
by zackattack 17y ago
How about fixing the memory leaks before revamping the UI? the ui is fine.
- vilya 17y agoDifferent teams, different talents, maybe? Are you saying the user interface people should just stop working until the developers have done their bit?
- bricestacey 17y agoThis is a good point, but Firefox is essentially unusable in its current state unless you're a masochist and enjoy poor performance so working on any additional features is a poor decision.
- sid0 17y agoI use it everyday, so it clearly isn't "unusable" -- and no, I don't enjoy poor performance. I don't see Firefox performing poorly at all.
- NathanKP 17y agoI totally agree. They should also work on making a true 64 bit version. As it is Firefox can not compete with 64 bit Safari running on Mac OS X. Firefox is going to fall behind unless they go 64 bit as well.
- tree_of_item 17y agoWorking on the UI doesn't stop them from fixing memory leaks. There are different people working on different parts of the browser.
- dangrover 17y agoDo we know that they're definitely leaks? I thought they just had some crazy caching or something. How did that story turn out?