2 ms·
Judging by this sub-thread, the process really is harder to explain that it appears on the surface. The basic idea is simple but the implementation requires dee
by Tagbert 2y ago
Judging by this sub-thread, the process really is harder to explain that it appears on the surface. The basic idea is simple but the implementation requires deeper knowledge.
- diggan 2y agoBut why would you discuss the implementation to end-users who probably wouldn't even understand what "implementation" means? The discussions you see in the subthread is not a discussion that would appear on less-technical forums, and I wouldn't draw any broader conclusions based on HN conversations in general.
- kccqzy 2y agoBecause the implementation leaks to the user experience. The user at least needs to know whether after running the utility, the duplicate files will be gone, or whether changing one of the files will change the other. Symbolic links, hard links, ref links are all part of the file system interface, not the implementation.