Hacker News new | past | comments | ask | show | jobs | submit login

I mostly use Carbon Copy Cloner, PathFinder, ditto and rsync because if I try to copy anything more than a few files it's like I'm running MacOS 9 and I have to babysit the copy like it's a five year old riding a bike with training wheels.

It's pretty clear whomever is leading MacOS dev efforts has been given the directive to not commit any new resources to the MacOS Finder.

For organizing files, I use File Browser Pro (iOS/Apple Silicon), Leap, DevonTHINK and anything else except the finder and tags which have never really worked very well.

There are bugs in the Finder and Disk Utility that have persisted for multiple OS releases and I simply don't trust GUI file management tools in modern MacOS.

In my view, Apple has decided to kill the Mac as a tool and wants everyone to use their Apple devices as consoles except devs who have to put up with being treated as second class citizens while Apple simultaneously uses the same lot of folks to do QA during "public betas".

As an Apple follower for decades, I'm running away from the platform and have recently replaced iCloud (for all intents and purposes) with Syncthing. I use old Intel Macs as daily drivers because you can't really multitask effectively with Apple Silicon -and- work with files because, well, memory contention is still a problem with iGPUs just like it always has been. The speed-up of the much vaunted Apple Silicon has EVERYTHING to do with the physical proximity of the processor cores to the DRAM except when you have a lot of process running then the kernel panics because memory contention issues with storage since MOST storage has to be on the USB bus and you can get into situations where the Mac can't keep the files system consistent because APFS, snapshots and Time Machine are a fuxxing disaster... sorry folks. /venting.

I think Jeff should try ssfs with disk images on either end to get closer to 125 MB/s.




> It's pretty clear whomever is leading MacOS dev efforts has been given the directive to not commit any new resources to the MacOS Finder.

Funny to say, because I just noticed the other day that as of the latest macOS version, Finder directory copies now have some kind of progress metadata (as an xattr of the top level copied folder?) that allows you to cancel [or presumably fail due to network loss] and then later resume copies.


This is both a blessing (when it actually works on a huge transfer) and a curse (when things are being weird, usually network issues or a flaky remote connection, and you can't remove the weird greyed-out folder).


> and you can't remove the weird greyed-out folder

I'm not sure I've run into this state, but I would guess it would work to toggle your wi-fi off to trip the folder over into the "transfer failed" state (where it's no longer greyed out, and instead displays the little "Retry" emblem on the filename), and then delete it.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: