[hakfoo]

There's a very reasonable argument behind that, though.

"Sending" a file to another disc or on the network is non-transformative. At the far end, it's still a file.

But "printing" is inherently transformative-- you're expecting to get something clearly not a file (print-to-file pseudo-printers excepted).

I can see the desire for minimalism-- having seperate rows for "share/send" and "print" is, well, two seperate rows. But if you offer adaptable and configurable interfaces, I could see suppressing one or both depending on context or user preferences. (You have no external drives or registered share-recipients? No "Send To/Share")

[opan]

Obligatory:

https://retrohacker.substack.com/p/bye-cups-printing-with-ne...

[benj111]

Maybe I've been in Linux land too long but sending a file to a printer seems pretty obvious to me. Yes it's transformative in a way, but you could equally argue that my word document with A4 layout is a digital version of a document, and the print out is equivalent.

To me there seems to be more difference between sending and share. One is pushing something somewhere, the other implies making it available for someone/thing to pull.

I'm not particularly saying you're wrong btw. We are talking metaphors, and there's no 'correct' way to do it.