I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Something I mentioned in a different comment, rsync behaves the way cp does on a Mac. So for people used to rsync, it's not a surprise, and GNU cp is the surprise!
I think it's telling though that there are so many articles about rsync warning you you can screw up if you don't get the slashes right - the majority of people over the last couple of decades have been used to doing it the GNU way.
There's also a reason rsync behaves that way, and it too is something I'd expect. You syncsource-directory to destination-directory. As with any other form of syncing, it would be expected that you'd have two folders which are made to match one another.
"Copy X to Y", find X in Y.
"Sync X and Y", find X and Y are identical.
Simple.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Something I mentioned in a different comment,
rsyncbehaves the waycpdoes on a Mac. So for people used to rsync, it's not a surprise, and GNUcpis the surprise!I think it's telling though that there are so many articles about rsync warning you you can screw up if you don't get the slashes right - the majority of people over the last couple of decades have been used to doing it the GNU way.
There's also a reason rsync behaves that way, and it too is something I'd expect. You sync
source-directorytodestination-directory. As with any other form of syncing, it would be expected that you'd have two folders which are made to match one another."Copy X to Y", find X in Y.
"Sync X and Y", find X and Y are identical.
Simple.