Comparing Windows uninstallers, getting upset and then deciding to make my own
An “everything” software listing and uninstaller front end for the various install methods (nuget, steam, msi, …) to see everything in one place is an excellent idea. Even better if it allowed plugins so you could add methods (e.g a developer might want a node env listing). It should stick to being a front end though and not try to be too clever when it comes to deleting things.<p>A misconception is that it’s possible to accurately determine whether something can or should be removed, when it’s usually impossible. The only thing that can uninstall windows software in general is the installer that installed it (if it’s correct), or a program that at least observed and recorded the installation of it.
Any software that claims otherwise is lying, and at best it will fail and at worst it will make a mess of your system.<p>These days it’s more and more common to completely ignore the windows installer system and install per-user to app data, which has the benefit of allowing a better self-updating experience without elevated permissions, and lower risk of pollution of system files.<p>The worst offenders in my experience when it comes to traditional windows installers are those that are <i>not</i> using Windows Installer but instead simply act as scripts dumping files and reg entries without concern for transactionality, sharing etc. For example some flavors of installshield and similar.<p>The Windows installer system for all its flaws IS a pretty robust - but quite complicated - system for managing installs. The problem is that it’s either unused or misused, which is a consequence of it being too complex I guess.