Linked by Thom Holwerda on Sat 10th Jun 2006 22:28 UTC
Last week's column was basically a rant about things that bothered me about Ubuntu's GNOME/Linux combination. Besides the usual 'I do not experience the problems you have, so you must be an anti-GNOME troll!' and of the course the ever-present 'How on earth can you complain about Free software!', it did what is was supposed to do: bring problems under developer's direct attention (for instance, Evolution's UI maintainer emailed me, asking for more clarification). Now it's Apple's turn. Here is a list of problems I find the most annoying about Apple's Mac/MacOS.
Thread beginning with comment 133053
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2006-06-13
Two other reasons to do a complete uninstall:
1. You've borked the setup for the program and can't figure out how you set it up that [non-functional] way, but you want it to work again.
2. You're experiencing a bug and want to verify that it occurs with a clean install through a repeatable set of steps
Without a functional uninstaller, this can be rather difficult. With something akin to Debian's aptitude purge, it's relatively easy to clean up system-wide files (user files are a different story, but hopefully those are relatively easy to deal with, as they're all under ~/.appname or something similarly identifiable).
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-06-13
The only reason I can see for not removing configuration files would be that I'm uninstalling an application in order to reinstall it, and therefore do not want to lose my configuration.
What about applications that install kernel extensions? Sure, they are few and far between, but a kernel extension has the potential to affect the system in ways that configuration files can't.
Just a thought...