The copy command is called "copy" which kind of makes sense? I remember once seeing a colleagues .bashrc with things like "alias copy=cp". Flags won't work the same way of course.

Sure "chcp" is a mouthful, but "del" or "erase" makes as much sense as learning that "rm" is short for remove. You pick up either convention quickly enough, except that I'm constantly using "where" when I meant "which". Maybe I should make an alias or something.

Don't get me started on powershell's look-we-can-use-proper-words-lets-see-how-long-we-can-make-this.

I know what you mean but everyone does this.

Apple has Pages, Numbers, Keynote, etc. Google has Drive, Docs, Sheets, etc. Meta has Messenger. Far too many examples to list.

Conversely, it would be ridiculous to use non-obvious names.

In fact you are right! Somehow This didn't register. Thank you.

>I have no idea how this flys.

They aren't trademarking it and probably can't.

But there's no reason they anyone can't use generic naming for their products. Many software applications do and quite frankly its more descriptive to attracting new users than coming up with non-real names.

I would aruge the only reason made up names exist is to keep marketing departments employed trying to explain to users what they are needlessly.

The one I love is Microsoft's project manager, MS...

...wait for it...

...Project.

Was charged with managing a department-wide installation about fifteen years back, now. You want to have fun looking for relevant docs, try a search on "Microsoft Project". Good times!

I think the one exception to Microsoft's generic naming convention is Excel. Visio probably qualifies, too, but they bought that from someone else.

Oh, and I guess PowerPoint, too.