A defining difference between macOS and iOS, the command line depends on constancy of file names, and consistency of paths. iCloud breaks both, as well as Finder aliases.
aliases
Creating and resolving Finder aliases is straightforward in Swift: here’s how alisma does it.
Create a Finder alias from the command line, and resolve them to full paths – a new free command tool, with source.
Do you know when it would be best to use a hard link? What’s the difference between a Finder alias and a symbolic link? And where to High Sierra’s new clones fit in?
First there were inodes, aliases, and links. Finder aliases already use the volfs file system, but Apple wants us to switch to its opaque Bookmarks
Sierra brings undocumented weirdness to the Finder, with a folder that is, but it isn’t, and improved Finder aliases, which don’t work as well. Yet.
There were 2 serious incompatibilities when Sierra launched: ScanSnap which is now fixed, and Dropbox. How’s Dropbox doing now, then?
Do you know the differences between an alias, hard link, and symbolic link? Each has its uses, and understanding them is important.
Unravelling References attributes, and making backlinks easily.
Is there an easy way to create aliases in the Finder?
The Eclectic Light Company 