undefined | Better HN

0 pointsSoftwareMaven13y ago0 comments

OS X has a ~/Library directory that houses application settings and much else. It is hidden by default.

There is no question there is a need to have a place that "plebeian users" can't access. IMO, dot-files and dot-directories are as good as anywhere.

0 comments

DeepDuh13y ago

OSX, because of its big corporate watchdog, and the separation of the 'GUI' layer and the unix layer, has the cleanest directory structure by far IMO. Most of the times you don't even need a manpage or google to find out how to repair a misbehaving application - just delete its plist in ~/Library/Preferences, possibly also its ../ApplicationSupport directory. The OSX defaults system is so well designed, every time I need to do support on other systems I just ask myself why not every OS works this way. I can understand why Linux is the way it is and I like that too (for other reasons), but it at least shows why the Windows Registry is such a bad idea.

DeepDuh13y ago

Why can't I reply to some comments? That comment about the new sandboxed folder structure made me realize he's right. What's going on with all those symlinks inside the container directory?

This just shows to me what a bad idea sandboxing is for those kind of apps that are supposed to interoperate with the whole system. Is there even a security benefit vs. pure unix permissions if you sandbox the filesystem but then you link in tons of crap that could be potentially attacked?

Macha13y ago

It's to do with comments that get deeply nested quickly, presumably to prevent back and forth flame wars and the like. If you really want to reply to such a comment, click "link" and there is a reply link on the that page, or just wait.

rahoulb13y ago

> This just shows to me what a bad idea sandboxing is for those kind of apps that are supposed to interoperate with the whole system.

Isn't the point of sandboxing specifically to prevent apps interoperating with the whole system? (I've not really paid it much attention so far)

1 more reply

pjmlp13y ago

To be fair, that filesystem structure was already available in NeXTStep.

dchest13y ago

had the cleanest directory structure until 10.8:

~/Library/Containers/com.apple.Preview/Data/Library/Application Support/Preview

~/Library/Containers/com.apple.Preview/Data/Library/Preferences/com.apple.Preview.plist

X-Istence13y ago

Isn't this change because of app sandboxing?

j / k navigate · click thread line to collapse

0 comments

DeepDuh13y ago

Why can't I reply to some comments? That comment about the new sandboxed folder structure made me realize he's right. What's going on with all those symlinks inside the container directory?

Macha13y ago

rahoulb13y ago

> This just shows to me what a bad idea sandboxing is for those kind of apps that are supposed to interoperate with the whole system.

Isn't the point of sandboxing specifically to prevent apps interoperating with the whole system? (I've not really paid it much attention so far)

1 more reply

pjmlp13y ago

To be fair, that filesystem structure was already available in NeXTStep.

dchest13y ago

had the cleanest directory structure until 10.8:

~/Library/Containers/com.apple.Preview/Data/Library/Application Support/Preview

~/Library/Containers/com.apple.Preview/Data/Library/Preferences/com.apple.Preview.plist

X-Istence13y ago

Isn't this change because of app sandboxing?

j / k navigate · click thread line to collapse