Historically I thought that Mac OS resource forks (and later, application bundles) were a great way to organize data for a GUI-first system. They basically stand in opposition to the insistence on dropping .DS_Store files all over my FAT-formatted media. Sure the boring filesystems don't support for forks or attributes, but they are exclusively used to interface with non-OSX machines!
My 3D printer really doesn't need more garbage to fill its little brain up with when I'm just trying to print the Most Recent file. And my Ubuntu Live flash drive is really not a reasonable place for this either, I just needed to copy over a BIOS update...
So now some change(s) have the Finder insisting on writing AND THEN READING BACK TO CONFIRM extended attributes on a file that doesn't really exist on the target in the first place. The UF2 file is just a bunch of pre-formatted packets and only the payload bits get written to executable flash and everything is otherwise forgotten. The first work-around discussed, cp -X, doesn't involve the Finder but still results in harmless errors? "An error will be thrown in the Terminal window, and you’ll also see the normal “Disk Not Ejected Properly” error notification at the top right". Somehow rsync is instead the right tool for the job?
On the other hand... WHy are we tunneling a communication channel over a USB filesystem?!? couldn't we have Nice Things1 instead?
-
a USB standard for writing firmware that major OS vendors still agree to expose as a psuedo-block device for drag n' drop or arbitrary file writes, but could also be used in a bidirectional fashion for richer interaction and configuration? but make it discoverable instead of driven by vendor specific, windows-only applications?