jbrooksuk wrote:I've closed #373 in favour of #379
Thanks, hopefully HQ reads through the issues
I'd like to summarize a discussion we had internally about this issue, maybe it's useful for others:
1) On some Windows configurations, atomic saves are outright buggy and dangerous
2) On Linux, file metadata is sometimes lost (i believe this is over mounts only, but not sure)
3) On all OS's there are cases where config-directories allow edits, but not file creates (we have examples in our shop). Atomic save doesn't work at all in these cases.
4) File monitoring tools, as noted in the issue as well, depending on modify-events are confused since modify, create and delete events are all generated
5) Saving takes substantially longer over certain mounts
6) It's not a useful feature at all, the likelyhood of the rename failing during outages (esp. true on osx's fs) is higher than the likelyhood of dataloss on filewrites
Our conclusion is that not only should this feature not be default. It should not be in there at all.