News for hackers. Stuff that matters.
Re:Rob Pike: the origin of dotfiles by onli on Friday August 03, 2012 @05:20AM (#4333238)
> The first benefit is that it removes clutters from your $HOME.

Invisible clutter? That's a strange concept.

But the rest of your point indeed makes sense. It still is easier and probably comment to backup the whole $HOME. But those points you can see as a benefit, though not obvious.

Re:Rob Pike: the origin of dotfiles by lubutu on Friday August 03, 2012 @06:44AM (#4333443)
As Rob mentions in his post, the more dotfiles there are in $HOME the slower path resolution for any subfiles becomes. How do we navigate to ./src? We open the directory and read all the entries until we find the one called "src". What happens if we encounter a morass of dotfiles beforehand? src takes a while to find. The clutter may be invisible to you, but it does gum up the works.
Re:Rob Pike: the origin of dotfiles by kbolino on Friday August 03, 2012 @08:18AM (#4333650)
For what it's worth, most modern file systems (JFS, XFS, ext4, reiserfs, btrfs, ...) have logarithmic (or better) directory lookup times. This is achieved using hashes and b-trees (or even hash tables).
Re:Rob Pike: the origin of dotfiles by lubutu on Friday August 03, 2012 @10:56AM (#4334286)
Fair point. Though anything using the standard POSIX dirent API would still get the performance hit (even if path resolution doesn't).
Re:Rob Pike: the origin of dotfiles by duaneb on Friday August 03, 2012 @06:53AM (#4333465)
Unless you have many thousands of files, I can't imagine you would ever notice a slowdown.
Re:Rob Pike: the origin of dotfiles by Edootjuh on Friday August 03, 2012 @07:34AM (#4333544)
It's not invisible when you're actually looking for an invisible file.