I don't see the problem with that. It's better then them releasing it then having to patch a crap load of ****. Anyway, it's not like you're forced to use the RCs.
3 RC releases in less than a month .. give me a break
What's the problem?
The deal is that even the first RC was believed to be "done". Then bugs were found when submitting it to a broader audience, etc. It's not at all like Microsoft that releases their "RC's", knowing they have like 100 bugs remaining to fix, but that they're in a stage of feature freeze. They're rather releasing an RC with zero known bugs, finding one or two, and obviously this will be quite quick to fix, and this will continue until none are found anymore.
If you get a headache by this, don't care about following the RC's. It's really simple.
I had issues with RC2. CPU Max outs @ 100% on some sites for no reason, as well as a weird Work Offline bug that made FF come out of hibernation in Offline mode. Was annoying. Hope it's fixed.
I had issues with RC2. CPU Max outs @ 100% on some sites for no reason, as well as a weird Work Offline bug that made FF come out of hibernation in Offline mode. Was annoying. Hope it's fixed.
Firefox seems to have had this bug for years now. It never gets fixed. Its the number one things I hate about Firefox, the 2nd thing I hate is that every little update to Firefox breaks every single addon you have installed which is just stupid.... even the firefox skins.
Google Chrome? But yes, that browser doesn't have good extension support yet, just the rudimentary pieces. You can still get adblocking to work well with it though, so it's not such a huge issue to me.
Yes, there's a point with this, and that's that each RC of Firefox is thought to be final, for real. They really are candidates unlike what Microsoft call release "candidates", where they're still aware of bugs to fix. So as a result of this, they're releasing them without e.g. special build strings, as they assume they're going to be done when releasing.
Yes, there's a point with this, and that's that each RC of Firefox is thought to be final, for real. They really are candidates unlike what Microsoft call release "candidates", where they're still aware of bugs to fix. So as a result of this, they're releasing them without e.g. special build strings, as they assume they're going to be done when releasing.
Oh I see. So anyone using Firefox RC3 is actually using the Official release of firefox 3.5. *Goes to check the website* I don't see it on the site.
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.
Fixing stuff in non-final releases is bad now?
Cry me a river. Just wait until final then.
What's the problem?
The deal is that even the first RC was believed to be "done". Then bugs were found when submitting it to a broader audience, etc. It's not at all like Microsoft that releases their "RC's", knowing they have like 100 bugs remaining to fix, but that they're in a stage of feature freeze. They're rather releasing an RC with zero known bugs, finding one or two, and obviously this will be quite quick to fix, and this will continue until none are found anymore.
If you get a headache by this, don't care about following the RC's.
Firefox seems to have had this bug for years now. It never gets fixed. Its the number one things I hate about Firefox, the 2nd thing I hate is that every little update to Firefox breaks every single addon you have installed which is just stupid.... even the firefox skins.
Oh I see. So anyone using Firefox RC3 is actually using the Official release of firefox 3.5. *Goes to check the website* I don't see it on the site.
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.