For me these have entered into my must haves
- BetterDisplay: For better scaling support for external monitors
- Rectangle: To be able to use a mouse to drag and snap windows
- Pixea: To be able to double click an image with a mouse in any folder and then use arrow keys or scroll wheel to proceed to the next file in the folder. Replaced the stock preview with this.
Something I’m looking for now is the ability to use the forward and back buttons on my mouse when I’m in Finder and want to go back to the previous folder I was in. Doesn’t work in Safari either. Works in good old dependable Firefox though.
And separate volume controls for each applications.
Yeah, I do like the option of if I uninstall something to get rid of everything so it is back to the state it was before instead all these random misc and now unneeded files. I did some searches and lot of users were wondering why this functionality isn’t present already.
The problem is AppCleaner is effectively guessing based on file name (and potentially other metadata) what to get rid of, you have to use your brain to check the list of what it is proposing to delete (hence why they show it to you and make you check the additional boxes). Someone who is actively seeking out the app to do something like this is more likely to check, but if it was a default functionality from Apple, many users would just ignore it and delete everything, even if it’s something they’d want to keep. Apple’s ethos of how they view users is also not predisposed to this.
It’s also notable that many things get left behind even after unintsalling apps in Windows. Sometimes the manifest just doesn’t encompass everything an app will spit out during its existence on your device.
But if it was a default functionality from Apple, presumably apps would be packaged, installed, and run in such a way that the OS is aware of what files it’s creating and use that context to clean up after themselves properly when uninstalled.
The OS doesn’t create the files, the application does. The OS would need a way to track what’s being created throughout the lifecycle of the application on the device. For example, at install the app may just put the .app bundle in /Applications and then complete. During first startup, licensing, saving, customization, and at other various indeterminate points the application might create preference files, directories/files in /Library/Application Support, etc. macOS does log things but those get rotated, if you just keep infinite logs you end up using up a ton of space.
Apple could try and require that every Application provide a manifest of where it may put all files, but I don’t really now how they’d enforce it and this is still subject to error and may result in the wrong thing being deleted. Also, keep in mind there are some shared folders and file between apps within the same suite. For example, Autodesk puts a lot of things from various apps into /Application Support/Autodesk.
Another thought is, sometimes you don’t want it to delete all associated files created. Often applications create a save directory in /Documents. I think SPSS or Stata might do this (haven’t work with them for a bit). So if /Documents/Stata has all your work and some automated Apple uninstaller removes it, that isn’t ideal. It may even be disadvantageous to remove a plist file. For example if you’re installing an old version of an app for a new one, it may use the same plist with your settings so you don’t have to reconfigure the app. There’s just a lot that can go wrong if you automate this process for what is often relatively little gain.
When an application wants to create a file, who does it ask for permission? Who facilitates finding a spot on the disk for the new files to go?
Frankly I can’t speak to the overhead for managing it but the OS is aware and could very much keep track of which applications own what. As for shared directories if they know the specific app owner obviously just remove files from app A but keep the directory if app B also uses it.
As for configuration files and save data, these are generally located in consistent places but ultimately that’s going to be a responsibility of the app developer to keep with standards for where those config files go so they can persist through reinstalls.
‘Do you want to delete this application completely, or would you like to keep configuration files and save data?’
But Apple doesn’t really care, they want everything to feel seamless and look pretty. Actual functionality is a second thought.
It has permission via certificates and writes/copies either via bin commands (cp) or the user does it (drag app to applications). Applications don’t own files within macOS. It’s UNIX methodology where it’s a user/group/everyone situation. Often files will be owned by “system” or the logged in user that installs them. The OS would need to snapshot what is done during installation (which is actually done by packaging utilities like composer) but this is also prone to error because it tracks all changes during installation, so if you’re modifying files with other apps while the current installer is running in the background it will capture that. And I think you’d be surprised how many apps keep files in non-traditional places.
It’s just not as straight-forward as you think it is and no OS really does this will. Windows uninstaller often misses a lot of registry keys and programdata/appdata files. Linux will only uninstall what it install during the apt/dnf/whatever process. Even iOS leaves things behind like folders in Files.