> on Macs the CMD key is simply a poor man's CTRL key, except when you are in a terminal, where you have to use CTRL again...
Let me check.
Cmd-F in Notes.app, finds things in the current note.
Cmd-F in Terminal.app, finds things in the current terminal session's history.
Cmd-C in Calendar.app, copies an event.
Cmd-C in Terminal.app, copies the selected text.
Cmd-T in Finder.app, opens a tab.
Cmd-T in Terminal.app, opens a tab.
Cmd-W closes the current window/tab. Cmd-Q quits the app. Cmd-S saves. And so on, in any app, tracing back to 1984 or so.
Whereas Ctrl-C, Ctrl-T, Ctrl-F, Ctrl-S, on Windows/Linux... all do wildly different things, depending whether you are in an xterm, cmd.exe, a game, Emacs, or some other app.
You know what else? Ctrl-C in Terminal.app does the same thing as Ctrl-C in an xterm. This sort of thing is consistent in every app. You're literally having your cake and eating it too.
Windows couldn't use Ctrl-W to mean "close the current tab" in every single application, because - indeed, in a game, holding down Ctrl could mean crouch/sneak, and W to move forward. Windows could've chosen to use Win-W for that, but ignored the opportunity.
> anyway, this is just a coincidence
One of these patterns visible here is deliberate design, the other is piled up coincidences. I don't think it's that easy to confuse one for the other?