It’s not much different to macOS in that regard.
#Appcleaner 3 free#
But then the app is free to write its configuration data to any registry key it likes (usually ones named after the app), or to files in ~\AppData, or perhaps C:\ProgramData. Windows installers/uninstallers may create/remove some registry entries, but those are typically entries for file associations and the installed program list, and perhaps some global settings. The Windows registry is a simple key-value store, just like the macOS defaults system. Of course they ruined all that with ~/Library//. Like dragging an "Application" or a CD-ROM into the Trash to get rid of it. > The whole Mac idea was that there's no "uninstall process" with opaque windoze registries etc what the Finder shows you is simple enough for an average user to understand. Most apps need to save some kind of settings and/or transient data files. I don't see how you could possibly claim that the user library "ruined" anything. It turns out that Apple installer packages do include a manifest (cutely called a BOM) of package contents, but users don't typically keep package installers around after completing installation successfully, and it says nothing about files that may be written by the app itself while in use. But I also think that apps should have some kind of associated file manifest, which you can use to automatically clean up after the app, or at minimum get a definitive list that you can go through manually or with a script. I think I agree that the default behavior should be to leave all that data on the user's system. Consider that sometimes people do actually want to clean up all artifacts of an installation, and don't want to go digging around in a bunch of machine-generated directories trying to guess what to delete.
0 kommentar(er)
