View Single Post
  #2  
Old March 19th 09, 01:56 PM posted to alt.comp.periphs.mainboard.asus
Kyle
external usenet poster
 
Posts: 86
Default Registry cleaners ???

"Zootal" wrote in message
...
| I am constantly amazed or at leat I used to be that software
vendors
| cannot supply a decent removal tool that completely uninstalls
their
| product. I mean, what's so hard about removing everything since
they
| decided where to put it in the first place.
|
| Because it takes time to write code that does that, and their
managers don't
| want them to take the time to do it. Who cares if the registry get
bloated?
| I maintain software that is buggy as hell. It remains full of known
bugs
| because managers don't want to bother fixing bugs that don't pop up
very
| often. It's not the fault of the coders (for the most part). It's
the bosses
| that say don't fix this, don't do that. It costs money to fix it,
and it's
| not worth fixing.
|
|

Your point is noteworthy, yet subject to further commentary. It IS
the fault of the "coders" as writing software that is "good" software
the first time around takes a concerted effort, and too many are
either lazy or not sufficiently skilled to do it right in the first
place. I realize there are deadlines and project cost constraints, I
used to write a lot of software, but such excuses are insufficient to
justify badly written software. I deal, in my business, with software
people quite often and am surprised (and disconcerted) to find out how
few know how to create a top-down structured flowchart for their
software (probably because such was never done, and trust me, software
becomes a spaghetti mess quite quickly when written without some
underlying flowcharting effort in the beginning).

In particular, it is quite easy to delete an entire registry key
without having to track individual data value entries stored beneath
that key, and many uninstall programs fail to do this. How many times
have you uninstalled/reinstalled a program only to find all of your
"original" settings are still there? This is due to an entire
registry key (and data values stored under that key) under
HKLM/software/suppliername/productname or
HKCU/software/suppliername/productname still remaining in the registry
after the uninstall occurs.
--
Best regards,
Kyle