There's also the fact that you see questionable marketing tactics being used. Now if I am writing a registry cleaning program, how do I systematically/programmatically go about evaluating the countless possible combinations of registry entries these programs might make? Do I have some massive database somewhere that has a listing of every registry entry created by every single Windows program? If so, how do I manage to cram that much info into such a small program? How often do I update this database, as new programs are created? These are just a couple of basic questions, which will branch off into several other areas if you keep following the rabbit hole down, and I've never come across any answers. There's probably more, but just for example. For the sake of argument we can assume there are 1 billion unique programs for Windows. I would say it's more that they are generally a solution in search of a problem, and along the way may create problems. Don't programmers sometimes use "hacks" or poor coding technique that can register as errors in certian utility programs? That is another reason not to use cleaners. Even if Microsoft can't perfect one (they have the most to gain) then it's probably irresponsible for a third party to try to make one. So you're saying that they often cause more harm than good.
0 Comments
Leave a Reply. |