In terms of managing programs/packages, what is wrong with Add-Remove Programs/Programs and Features? I've always found these to be satisfactory. Or am missin

In terms of managing programs/packages, what is wrong with Add-Remove Programs/Programs and Features? I've always found these to be satisfactory. Or am missing the point here? In terms of automatically retrieving the correct dependencies, I can see this being pretty useful, even if most programs already automatically install the dependencies or at least let you know that you don't have them. Maybe I'll find myself in .Net framework or MS C++ distribution hell a little bit less. The same problem, with missing or incorrect shared libraries, seems to happen just as much when I am on a Free/Net/OpenBSD system. And the workflow for installing a Windows program is fundamentally different from the *Nix eco-system; as the former is mostly closed while the latter open, you have to be much more discrete when installing on Windows. Maybe I am using Windows differently than a lot of other people even if I consider myself a "power" user. I've always felt much of Windows' power and usability came from it's GUI focused experience (forgetting the maddening changes that can occur between versions). Post: after writing all that, I looked at Programs and Features (on windows 7 now) and I think the biggest advantage of something like this would be mapping out dependencies, even if I don't think I've ever deleted one by mistake. Still, it would be nice.