It not only takes a long time to start up and play its opening animations, but when you cancel it, it SLOWLY animates and cross fades back to the starting place, so you LOSE the time and location context that you laboriously browsed to, and then you have to take even more time and effort to get back to where you just were. No, that would be too easy, and you'd miss out on all that great full screen animation. You can't just quickly Alt-Tab to flip back to another app to check something before deciding which file to restore and then Alt-Tab back to where you were. It even sadistically blacks out every other connected display, and disables Alt-Tab, as if it was so fucking important that it had to lock you out of the rest of your system while you use it. I DO NOT CARE for it taking over the entire screen with its idiotic animation, that prevents me from browsing current Finder folders at the same time or DOING ANYTHING ELSE like looking at a list of files I want to retrieve on the same screen. Time Machine's "Floating Time Tunnel" user interface for browsing backups and restoring files is such a useless pretentious piece of shit. I’d put my money on Apple’s SMB implementation being the root cause of this file corruption issue that has been all over the Reddit Synology user forums lately. If Apple’s own employees have this problem, it’s hopeless they'll ever fix it for customers. What’s even more funny, I have a friend who works for Apple and apparently they use NAS storage in some teams and deal with the exact same annoyances! Aside from the constant mounting and unmounting (fun!), it’s just plain unreliable and slow.Īnd people have been complaining about this for years. On MacOS, connecting to anything over SMB is a total nightmare.
Browsing huge directories of thumbnails is snappy, file and folder names appear instantly. On Windows, it literally feels like the NAS is an extension of my local hard drive. I have a Synology DS220+ and connecting to it from a Windows machine vs a MacOS machine is like night and day. What’s more likely, is Apple’s notoriously unreliable implementation of SMB causing the problem (and that’s the only option now that AFP support on Mac is dead) Filesystem likely doesn’t have anything to do with it.
0 kommentar(er)
