This reminds me how much I hate the go ./... magic custom (that means this and all recursive subdirectories).
We have the unix -r custom already. Now we have another, that makes no sense, that you just have to learn.
We have the unix -r custom already. Now we have another, that makes no sense, that you just have to learn.
For example, GNU cp uses -r or -R for recursive copy, but OpenBSD cp only uses -R. ls uses -R only (-r is listing in reverse order). scp uses -r only (-R is remote copy). rm allows both -r and -R.
But then, commands like mv or find don't support anything like -r or -R, they implicitly affect the whole directory structure. Bash has * (with shopt -s globstar) for globbing with subdirectories. Make doesn't support any concept of recursive subdirectory traversal.
Other software that supports -r: rsync, fdupes, zfs destroy, et c.
I'm not saying they're breaking spec, I'm saying they're being weird and divergent for no particular benefit (and at a quite obvious cost in terms of Google-specific learning curve, as Go is used widely outside of Google).
I often think that a substantial portion of my job is software archaeology...
There. I did just learn it without following a tutorial or somethin. It's so simple, easy to remember. It's even faster to write that -R or -r.