I did do a clean install and restoring my programs was easy because most of them are on a separate drive not another partition on the OS drive. So it becomes a matter of simply creating new shortcuts to the desktop. That way if windows decides to take a hike my programs, files, photos, receipts, serial numbers, music, etc are safe on a separate drive which gets backed up weekly to an external HD which periodically gets burned t DVDs. All of this takes less time than to type this (I am an incredibly slow typer)
I got scorched myself about five years ago and decided that ain't happening again!
Actually, separate drive / separate partition distinction is a small one. If windows gets fudged on C:\ doing a clean install back on C:\ the system really is not affectd in any way if D is another partition or another drive, with rare exceptions. Using a manufacturer's restore disk for example, in some cases, creates or uses D:\for temp files so anything there might be written over. But a normal OEM / retail install leaves D etc alone. The 100% safe way is to have C:\ for OS, D:\ for page file / temp files. Add letters depending on preferences for Programs, Games, Data, backups whatever.
My kids boxes are set up that way w/ 1 HD and every XMas, I do a fresh install of the OS on C:\ While many games are "self contained" and don't need reinstallation, programs however are a different story. Developer's annoying desire to create C:\ProgramFiles\Common\[myprogram stuff] annoys me to no end but the programs still require registry keys to be rewritten and this won't happen w/o a reinstall.
As for the original discussion, having been responsible for IT management both at the office and at home LAN's 12 machines, I have to admit to subscribing to the "Anything that comes outta Redmond before SP3 is a beta" mantra. My outlook on this is primarily focused on how much time I gotta spend away from my desk and at someone else's solving PC problems.
NT4SP3 is still the reigning champ in that department. Right now I am pretty satisfied and yet frustrated by Win7. For one, I asterisked my above mentioned mantra by just thinking of Win7 (Ver 6.1) as Vista (Ver 6.0) SP3. Second, it's the first MS OS ever to be faster than it's predecessor. Win95 was 40% slower than it's predecessor (W4WGs) and since then they've continually narrowed the gap finally elimination it with Win7 and actually going a bit faster.
But then there's the "bleeding edge". My son saved for about 6 months to build his "killer rig" and I convinced him to wait an extra month for October 22nd so I wouldn't have to do multiple OS installs. I have got the Event Viewer error messages / warnings down to about 2 from 14, but still have unexplained BSOD's and driver issues, some of which get no answers on a web search.
Also a bit frustrated by the absence of "Use Windows Classic" UI. I am tired of learning new ways to do what I have been doing all these years and the fact that Win7 still doesn't have the long promised new file system, nor is it the completely "modular" OS we were told it was gong to be.
As for the comparison's w/ XP, it's certainly a valid one. XP was version 5.1 to W2k's 5.0 .... also a "minor upgrade" as the 6.0 to 6.1 change we are seeing with Vista and Win7. Back when we rec'd our 1st XP machine, that box kept me busier than all the other machines (Nt4Sp6 desktops - some dual booting 98 / Win2k laptops) we had. With our 1st Win7 box in the door, this one is keeping me busier at the moment but that's the price of early adoption and an unfamiliar GUI.
Though it's faster than Vista, I have not felt compelled to stray from my other pC mantra in that a machine will get retired with the OS it came in on. Since it takes far more time to install an OS and get the quirks out than to actually build one, if I am going have more machines with Win7, I'll simply wait till the existing boxes have outlived themselves, retire them and build more machines.