News for hackers. Stuff that matters.
Re:Ideas on modernizing the open-source desktop by reddalo on Thursday September 24, 2026 @04:46AM (#49827977)
Modern macOS still lets you keep editing a file even if it's moved somewhere else, I think because file editing is done with the actual file ID rather than its bare location on the filesystem.

Windows, on other hand, prevents you from doing this in my experience.

Re:Ideas on modernizing the open-source desktop by ctippett on Thursday September 24, 2026 @07:10AM (#49828982)
Correct. It's not so much "modern macOS" though, it's a feature of APFS[1].

  > Most of us still think of file systems in simple terms, like HFS+. Duplicate or copy a file, and macOS copies all the data to a new storage area and makes that a different file. Thankfully, APFS is much smarter than that, and regularly – indeed, as a rule whenever it can – doesn’t copy any data at all. What it does is create a clone file, which is a bit like a hard link, in that the file record points to the same data as the original. Unlike a hard link, the clone is a separate file, with its own iNode.

[1] https://eclecticlight.co/2021/05/29/explainer-deduplication/
Re:Ideas on modernizing the open-source desktop by someonebaggy on Thursday September 24, 2026 @12:56PM (#49833495)
Linux can theoretically do this, but only if the editing application keeps the file open between saves, which they don't.

It also keeps a file around on disk with no way to access it as long as it's open.

When are we getting filesystem transactions.