To read all comments associated with this story, please click here.
I agree. I'm also thinking it might be a good time to update a slipstreamed disk, pull out the old cpu and blow the dust out of old Bess...give her a shot of adrenaline via a faster cpu off newegg and then install fresh.
Hopefully, that will tide me over until Windows 7 finally comes out.
How many are out there like me in a holding pattern regarding upgrading until Vista is a memory?
"Yes, an RC is very close to final production code, but it can theoretically still change."
Unfortunately, with Microsoft you have to shift all development cycles one step to the right, with RC falling right off the track altogether.
"Release Candidates" are released with the foreknowledge that there are still bugs to be fixed, and there will be code changes. An example was RC2, where the build number is placed in the My Computer's properties instead of "Service Pack 3".
This isn't just with their Service Packs either. This "release an RC as a beta" applies to almost all of their software. Then they change the code, and release the final without a real RC. The release candidate is the one you buy.
This shift unfortunately extends backward. Beta's are often very clearly alphas. Most of the software world uses RC to mean "Candidate for Release", and potentially, hopefully, no code changes.
Perhaps this is one of the primary causes of the release buggy, fix later problem* that Microsoft has fallen in to.
*Not really a business problem for a monopoly, as there is no need to compete.







Member since:
2005-11-30
Shrug. I think I'll wait until it appears in Windows Update. Not that I am aware of any problems with SP3; I am just not aware of any urgent need to update with something other than final production code. Yes, an RC is very close to final production code, but it can theoretically still change.