3 ms·
From a file access point of view in Catalina, the OS’ “left hand” still doesn’t always seem to know what its “right hand” is doing. For example, just today I t
by makecheck 7y ago
From a file access point of view in Catalina, the OS’ “left hand” still doesn’t always seem to know what its “right hand” is doing.
For example, just today I tried to save a file on top of an existing file, and when the system panel prompted me, I said Replace. That appeared to be accepted but after the panel closed the app failed to actually save, citing something about how I do not have access to the target file. I used the Finder to trash the old file and retried, and then it worked. From a user point of view, this is exactly the kind of work-around that should never be required, and I can imagine some people not even trying and just thinking everything is broken.
And as an app developer these things are even more frustrating because I literally cannot tell all the ways a user “might” have an issue anymore. How many awful combinations of file-related failures are there? How many obscure messages are possible, and is a message even displayed for every case?
If a system is really complex, it is not only hard to get it right once but it is really hard to keep it right over time. I am worried that all these special cases will just be fixed and re-broken for months on end.