Firefox GTK+ Integration
Posted May 27, 2008 17:03 UTC (Tue) by dskoll
In reply to: Firefox GTK+ Integration
Parent article: Fsyncers and curveballs (the Firefox 3 fsync() problem)
Breaking working code and slowing down fast code are consequences of making progress toward other goals that the developers believe are more important.
True, but what do users believe to be more important? And usually by the time you have a "Release Candidate", you've fixed up the obvious breakages.
As I wrote, I don't use KDE, so I'm not looking for a KDE/Qt browser. I do get alarmed when Firefox developers break stuff and don't undo the breakage. For example, I filed a bug asking for Firefox to default to the (fast) built-in filebrowser dialog (which still ships!) rather than the (slow and broken) GTK+ filebrowser, but met with a negative response. So the question is: If you ship a superior filebrowser, why do you choose to use the stupid one by default??
to post comments)