> Terminal has historical bindings

Keeping that as a default is silly though. Intentionally having poor UX that's unnecessarily confusing to new users because of "reasons" is why Linux can never become a credible consumer OS.

The poor UX comes from the browser using Windows shortcuts instead of something that's consistent with the rest of the environment.

Compare this to macOS, where copy and paste are consistently Cmd+C and Cmd+V. More generally, keyboard shortcuts tend to use Cmd. That leaves key combinations with Ctrl to their traditional uses in the terminal. Which is pretty convenient, as the combinations won't randomly change when you ssh to a remote Linux system.

Keeping ctrl-C as the binding for copy is silly though. Intentionally having poor UX that's unnecessarily confusing to power users because of "reasons" is why Windows can never become a credible developer OS.

Having different shortcuts for the same operation in different applications is just wrong.

> Windows can never become a credible developer OS.

For better or for worse it has been one for decades.

> Keeping ctrl-C as the binding for copy is silly though

Why? Also sure whatever, it can be something else as long as it is CONSISTENT.

> confusing to power users

Well.. Good thing is that "power users" know how to change default shortcuts and can use a different "power user" profile.

The shortcut is actually the same everywhere: Command+C

You obviously just switched it to mimic Windows, which is why it's "inconsistent"

You mean "Super/Meta + C" is the default for copy on Linux making the whole argument redundant? I don't think that's a default shortcut on Gnome or KDE....

You don’t break things that have been in place for decades, period.

No, you can fix them, though.

Of course if the developers of Linux/KDE/Gnome/etc. want to make their software unnecessarily confusing to new/less experienced users which would make inconsistent UX an intentional feature then you're right.

If I had to choose between pissing off experienced users and confusing new users, I’d take the latter. You can learn to context-switch.

If I’m in vim, I know that I have at least two sources to paste from; one with `p`, and one with Cmd/Ctrl-Shift-V.

> You can learn to context-switch.

Presumably experienced users know how to change shortcuts/profiles.

But that's fine, such a design philosophy just means that Linux will never become appealing to non-advanced users.

> (Ctrl-C is especially common, being "interrupt" or "quit".)

That is same for terminal in macOS. Mac uses cmd-C/V for copy/paste in gui, so it is not in conflict with ctrl in terminal. Which I find nice, but ctrl+shift is sufficient as well.

Ironically I use ctrl-c all the time on my Mac, so this makes sense — will try it out!