2 ms·
I think you meant to link https://lwn.net/Articles/899543/ https://lwn.net/Articles/899543/ (and HN discussion at https://news.ycombinator.com/item?id=32190032
by userbinator 4y ago
I think you meant to link https://lwn.net/Articles/899543/ https://lwn.net/Articles/899543/ (and HN discussion at https://news.ycombinator.com/item?id=32190032 https://news.ycombinator.com/item?id=32190032 ) instead of that single comment. It takes the security angle (which is frankly oversold these days, but that's another rant...), but also makes some very good points about the complexity they introduce --- which does, among other things, create security issues. FWIW, I don't hardlinks are a good idea either. (In FAT filesystems, it is possible to have "hardlinks" where the same data is referred to by multiple names, but those are actually errors and referred to as "crosslinked files".)
Without links, there's a 1-to-1 mapping between (absolute) paths and file contents. When operating on a path, there's no need to consider whether the API will act on the link or what it points to.