Live data from Hacker News

Making macOS Apps Uninstallable

notes.alinpanaitiu.com

51–60 of 208 posts

Re: Making macOS Apps Uninstallable

#51
post #20

Earlier quoted context omitted.

You can also just run apps from anywhere - network drives, removable disks, disk images etc., so the system can’t just delete settings for apps it’s currently unaware of.

Yeah I think the real problem is that deleting an app isn't uninstalling (which is sometimes a feature not a bug), but Apple provides no paradigm for actually uninstalling that deletes preferences too.

They do on iOS.

Re: Making macOS Apps Uninstallable

#53
post #29

Earlier quoted context omitted.

This is complete bullshit. Alfred 5.0 was released in July last year and the last update 5.0.6 was in December. Packal is online and a couple of packages were updated 1 week 6 days ago. And not only that, but to replicate most of Alfred's functionality in Raycast, you have to rely on plugins and hope they are both secure and maintained by somebody whereas Alfred's functionality is maintained by the Alfred team. Stop…

Different user, but I too “remember” first quicksilver and then Alfred shutter. Did I hallucinate that, or did it happen and later have a revival, or what?

Yeah I didnt knew much about alfred 5 tbh

Re: Making macOS Apps Uninstallable

#54
post #10
post #7

Earlier quoted context omitted.

The free AppCleaner was mentioned by another reader earlier in the thread, and I've been happy with CleanMyMac X.

AppCleaner is no good after you deleted an app by other means and it left crap on the hd tho… as far as I recall CleanMyMac was a paid closed course app?

[deleted]

Re: Making macOS Apps Uninstallable

#56
post #4
post #2

I recently had to uninstall some apps and it’s common for apps to litter files throughout /Library and ~/Library. The UX from early MacOS days is you can drag/drop the App to the Trash Can to uninstall it. Does MacOS actually clean up the misc. files applications leave at some point?

Nope, still leaves them behind. I’ve been using AppCleaner ( https://freemacsoft.net/appcleaner/ ) for years now and it’s a real neat (and free) app that’ll do a pretty decent job of cleaning up crud.

Well, if it's a really modern application it will leave everything in only one folder in ~/Library/Containers as part of the sandbox. Besides the obvious security advantages of the sandbox this makes cleanup a lot easier too.

Re: Making macOS Apps Uninstallable

#57
post #3

Earlier quoted context omitted.

I never had macOS remove those files automatically when dragging the app to the trash. I still have files left from 4 MacBooks ago (for apps I haven’t installed in a long time) because I’m always migrating the home folder. I guess they’re just expected to be left behind in case you change your mind and want to reinstall the app later. That way you’ll still continue where you left with the same settings. They’re inert…

> I guess they’re just expected to be left behind in case you change your mind and want to reinstall the app later. That way you’ll still continue where you left with the same settings. And if apps are well behaved, only writing tiny config files in ~/Library/Preferences/ and the like, it’s not really a problem. The amount of space taken up in that situation was tiny even when OS X 10.0 was brand new and 10GB was a c…

Yeah all the crap Adobe and Microsoft apps leave in /Library/Application Support/ for example. That's really a trash heap on a Mac.

Re: Making macOS Apps Uninstallable

#58
post #4

Earlier quoted context omitted.

Nope, still leaves them behind. I’ve been using AppCleaner ( https://freemacsoft.net/appcleaner/ ) for years now and it’s a real neat (and free) app that’ll do a pretty decent job of cleaning up crud.

This is just unbelievable. The billion $$ company cant just automate the uninstall procedure for their users? How hard would it be to auto delete the contents of ~/Library? Or have some periodic auto clean? one can always dream, no? I wonder how many users that have uninstalled VMware still have 30 gigs of unused VMs lying around on their disk.

~/Library contains stuff for lots of apps and they don't necessarily have to be in a folder with the name of the same bundle ID. Only sandboxed apps are much more strict about this.

Re: Making macOS Apps Uninstallable

#59

Earlier quoted context omitted.

That's also Apple's fault isn't it? App data should fall into an predictable folder regardless of the location from where is ran, if for whatever reason the app needs to use a different folder it should be something developers have to go to multiple hurdles to implement (e.g. specify in a manifest what files and where will them be stored, and explicitly specify it they should be automatically deleted or not after mov…

To be fair, the situation isn't much better on Windows or Linux. While at least they have a concept of uninstalling an application, you're still reliant on the developer actually getting it right and not missing some tempfile or something.

The filesystem doesn’t have rich enough metadata about temporary files. At least Windows has a file attribute for temporary files (FILE_ATTRIBUTE_TEMPORARY), although I’m uncertain how many apps actually set it on their temporary files; Linux/Unix/etc appears to have no real equivalent. I think ideally temporary files would have rich metadata - the ID of the process, session, and application/package which created them, and some kind of retention policy and expiry date. Of course, one could always use xattrs for that, but unless they are standardised few would use them. C library functions such as mkstemp/mkdtemp/etc could be enhanced to set metadata on temporary files. The OS package manager (apt/rpm/etc) could put an xattr on an executable with the UUID of the package, and then mkstemp could copy that to an xattr of all temporary files. Now if the FS also indexed xattrs, we could upon uninstall find all temp files owned by a given package and remove them.

Many mainframe/minicomputer file systems support file expiry dates, which is an interesting feature which Unix missed.

Re: Making macOS Apps Uninstallable

#60

Earlier quoted context omitted.

That's also Apple's fault isn't it? App data should fall into an predictable folder regardless of the location from where is ran, if for whatever reason the app needs to use a different folder it should be something developers have to go to multiple hurdles to implement (e.g. specify in a manifest what files and where will them be stored, and explicitly specify it they should be automatically deleted or not after mov…

> App data should fall into an predictable folder regardless of the location from where is ran In fact, App Store apps are guaranteed to do that (by being in a closed sandbox); that's why Apple has an uninstallation procedure only for App Store apps. > specify in a manifest what files and where will them be stored, and explicitly specify it they should be automatically deleted or not after moving the app to the trash…

Yeah the way they're doing this is a bit of a pain in the ass to be honest. Set up a new Mac and you have to do though tons of these popups. It causes popup fatigue and users start just clicking yes without even reading it. I've seen it many times. It defeats the purpose this way.

It reminds me very much of how they made fun of Windows Vista in the past: https://www.youtube.com/watch?v=MyGUrPxG1iM

I don't know what a better solution would be but I don't think this is it. And the documents and downloads folders are pretty arbitrary on Mac. Any user created folders don't get this protection.

I do love the way that sandboxed apps only store stuff in one folder in the ~/Library/Containers folder though. Even non-MAS apps that are sandboxed have to do that.

In fact the trick in this article doesn't even mention this, if you use it with a non-sandboxed app you're not guaranteed to uninstall everything for sure using this method.

Post reply on HN