On 17 Apr 2020, at 4:19, Marc Wilson wrote:
I hope you don't actually make this change... atomic save is desirable, even if you end up losing some metadata.
Disabling atomic save is not motivated by Timothy’s problem, but with APFS atomic saving can only be done by writing a new file and then replace the old with the new via
The problem with this is:
Some of the above should not be visible to the user, as long as the software handles it properly, but at least item 2 and 3 are user visible and IMHO a regression compared to pre-APFS where we had
exchangedata for atomic saves.
¹ This isn’t just real-time observing, but a build system may also end up doing more work because of this, if it supports globs to select input files or similar.