"Unfortunately not. OS X programs often spread their files all over the file system, with a mess of binary configuration files"
you're a bit misinformed. 95% of the OSX apps do not spread any files and do not need any installation. also, all the required files are stored in a single.app directory (except the preferences, which are kept under $HOME/Library/Preferences).
"possible netinfo entries (akin to the Windows registry...)"
i just browsed through my entire netinfo db with Netinfo Manager, and couldn't find any application-related entries, except for a few special user groups (ftp, daemon, clamav, mysql, etc). there are 154 apps in my Applications folder.
"There is no standard method in OS X to cleanly remove them"
yes, there is: - applications installed using drag'n'drop can be simply deleted. you may also want to delete the application's preference file under $HOME/Library/Preferences. - applications installed using an installer can be uninstalled by running the installer again, some installers even create an uninstall shortcut.
"Basically, the requirements of the piece of software would be heavily contradictory - dead-easy to use, but still incredibly powerful. Few such programs exist - because they are virtually impossible to make."
i know i'll be modded a troll now, but i just can't resist: - did you ever see a Macintosh? or a Garmin GPS unit? or a TiVo? or an iPod? or a BMW iDrive?
writing dead simple yet powerful software is no wizardry. you just have to concentrate on functions and workflows which are used by the customers in 90% of the time, and hide the power features elsewhere (keyword: RTM). if you present all the functions at once, you'll end up with a chaotic GUI. keeping the focus on the main functions will allow the people to use your product in an intuitive way, with an extremely short learning curve.
Slashdot Mirror
"a lawyer, and one of the smartest people I know"
a smart lawyer? isn't that an oxymoron?
what fucktard thought that custom optical discs would be a good idea?
The same fucktards that want to make pirating games difficult without breaking the game or your system.
you mean the same fucktards who still don't recognize the fact that offering value for the money is the best copy protection ever?
"Unfortunately not. OS X programs often spread their files all over the file system, with a mess of binary configuration files"
.app directory (except the preferences, which are kept under $HOME/Library/Preferences).
you're a bit misinformed. 95% of the OSX apps do not spread any files and do not need any installation. also, all the required files are stored in a single
"possible netinfo entries (akin to the Windows registry...)"
i just browsed through my entire netinfo db with Netinfo Manager, and couldn't find any application-related entries, except for a few special user groups (ftp, daemon, clamav, mysql, etc). there are 154 apps in my Applications folder.
"There is no standard method in OS X to cleanly remove them"
yes, there is:
- applications installed using drag'n'drop can be simply deleted. you may also want to delete the application's preference file under $HOME/Library/Preferences.
- applications installed using an installer can be uninstalled by running the installer again, some installers even create an uninstall shortcut.
"Basically, the requirements of the piece of software would be heavily contradictory - dead-easy to use, but still incredibly powerful. Few such programs exist - because they are virtually impossible to make."
i know i'll be modded a troll now, but i just can't resist:
- did you ever see a Macintosh? or a Garmin GPS unit? or a TiVo? or an iPod? or a BMW iDrive?
writing dead simple yet powerful software is no wizardry. you just have to concentrate on functions and workflows which are used by the customers in 90% of the time, and hide the power features elsewhere (keyword: RTM). if you present all the functions at once, you'll end up with a chaotic GUI. keeping the focus on the main functions will allow the people to use your product in an intuitive way, with an extremely short learning curve.