@monsieuricon yup, 30 years of Unix/Linux daily use and I still fail this one. Reminds me of USB Type-A 50% chance of plugging it wrong, but failing it *every* time.
BTW, @bagder started a separate thread on this and people are mostly getting it right on the first try - smh...
USB always needs three attempts:
1. Wait, this feels awkward, better try the other way round.
2. No, that's _definitely_ wrong. It _has_ to be the other way round.
3. Ahh...
@monsieuricon I had the same issue for a while.
Especially since I rarely use ln. I try to convince my brain that "-s" would mean "source" even though I know it actually means "symbolic link", just so I remember that the first argument right after the "-s" option is the existing, "source" file.
Yes, but what about tar?
Yeah, when I say it's like cp, that doesn't mean it's intuitive. I just have to repeat the mantra.
@monsieuricon @dgar every single time - my command history is:
$ man ln
$ ln -s blah blah
Cannot make it stick.
@monsieuricon haha while i'm in the "bro it's like cp(1)" crowd, i can appreciate where you're coming from because of memcpy(dest,src, ..).
i tend to find myself in this situation when it comes to unfamiliar assembly syntaxes, or even at&t vs. intel -- is it like cp(1) or is it like memcpy(3)
@monsieuricon Yes, it's a Sapir-Whorf thing. Some languages are verb-subject-object, and some are verb-object-subject. Yoda even speaks object-subject-verb (in the original, anyway; it's trickier in the German translation).
Don't think of it as a matter of abstract intuition, but as a matter of foreign language intuition. The intuition of consistency, not the intuition of essence.
pip destination=source. If Unix has been modelled after that, we'd be doing hard links by pip destination<=souce, and symlinks as pip destination<-source.