Linked by Thom Holwerda on Mon 16th Oct 2006 21:07 UTC
Mozilla & Gecko clones "The Firefox web browser has come a long way since the project was announced as a fork from the open-sourced Mozilla project. Version 1.0 was released in 2004 and quickly won critical acclaim for its speed, compatibility with web standards, and features. In a couple of years, Firefox managed to reach a milestone that its predecessor never quite reached: hitting 10 percent market share worldwide. Version 2 of the browser recently hit RC2, but the team is already making plans for 3.0. The Mozilla organization has set up a feature brainstorming web site that allows everyone to enter their favorite wish lists for the open source browser."
Thread beginning with comment 172272
To read all comments associated with this story, please click here.
FIX the damned thing
by deathshadow on Tue 17th Oct 2006 01:38 UTC
deathshadow
Member since:
2005-07-12

and by fix, I mean make it ACTUALLY standards compliant, remove the memory leak 'feature' (amazing how other browsers lack said feature), put the download manager in it's own thread so it doesn't hang the entire browser waiting on servers, and actually resolve ALL the existing bugzilla entries BEFORE tacking on new shit...

But then, that's not 'flashy' so of course nobody wants to actually work on that - the same problem plaguing most every other bit of software out there - as I'm fond of saying, if my 86 year old grandmother can figure it out, you are ****** done with the UI and features, so quit ****** with it and actually FIX the damned thing.

RE: FIX the damned thing
by smitty on Tue 17th Oct 2006 02:30 in reply to "FIX the damned thing"
smitty Member since:
2005-10-13

I mean make it ACTUALLY standards compliant
It's close enough for me - as long as IE is so much worse it really doesn't matter that much. It's good enough that you can get stuff working on Opera/Gecko/KHTML without much trouble. They should keep working on this, of course, but I wouldn't say this is a high priority.
remove the memory leak 'feature'
You can turn off the feature, although it isn't easy. Also, it isn't a memory leak, Firefox just doesn't seem to use the cache very efficiently.
put the download manager in it's own thread so it doesn't hang the entire browser waiting on servers
The download manager is by far the worst part of Firefox and needs tons of fixes, not just putting it in it's own thread.
resolve ALL the existing bugzilla entries BEFORE tacking on new shit...
That's a good way to never get anything accomplished. Half of the new features end up fixing old bugs anyway by removing that old code. There does tend to be a desire to work on new stuff rather than fixing bugs, but lets not go overboard the other direction.

Reply Parent Bookmark Score: 2