4 ms·

I'm curious about what "decades of UX research" improvements you are talking about, to me everything about the UI for text editors or browsers hasn't improved m

I'm curious about what "decades of UX research" improvements you are talking about, to me everything about the UI for text editors or browsers hasn't improved much in decades. If you have a laptop with just a touchpad, chances are you'll never get better than vim keybindings. Moreover, the keyboard layouts themselves are centuries old.

p-e-w 3y ago
> I'm curious about what "decades of UX research" improvements you are talking about Here's the most important one of them: Don't surprise me. Blend in. Look and behave like other programs. There are 50 applications on my system. Yours is one of them. If all other applications use 'Ctrl+C' for copying text, but your application uses 'y', then your application is the problem.
- spoonfeeder006 3y ago
  Thats a basic principle. But when you say decades of UX research you imply actual new ways of doing things And something innovative and effective would be both self explanatory and actually useful, so it ultimately gets adopted by others instead of simply surprising and confusing people
- akho 3y ago
  But Nyxt (which is modeled on Emacs, not Vim) would blend in for me. I spend most of my time in Emacs and Firefox; I would prefer a browser that blends in. I don’t know about 50 applications. The rest of the applications I use are more specialized, and have their own shortcut madness. Browsers ate most of the small stuff.
- gsinclair 3y ago
  That would be a problem if vim was installed front and centre on everybody’s computer and they were all expected to use it. That is not the case. You choose to use it, so you either accept, or better yet, embrace that y=copy, or you choose to use something else. Trying to objectively describe vim as a problem by invoking UX research is very funny. The end result of that logic is to rule out modal editors altogether.
- 8organicbits 3y ago
  What are you talking about? I suspect you haven't used vim recently. In the context of the command line Ctrl+C sends SIGINT, which usually interrupts/terminates a program. When I press Ctrl+C, vim shows "Type :qa and press <Enter> to exit Vim". All my command line programs handle it as SIGINT. Imposing Ctrl+C as copy would be inconsistent and surprising. If I'm using Visual Studio with vim keybindings Ctrl+C/Ctrl+V are still copy/paste (I suspect this is because VS provides this and the keybindings don't override it). I think every other editor with vim keybindings I've used preserves this behavior. Ctrl-C as copy is consistent with every other windowed program I'm running. Where have you encountered vim keybindings that don't permit this?
- xigoi 3y ago
  Vi is several years older than the Ctrl+C shortcut for copy. How could it possibly have know that Ctrl+C would become a more popular choice for copying?
- usrbinbash 3y ago
  > Don't surprise me. Blend in. Look and behave like other programs. There is hardly anything in the world that blends in better with everythign else, then a terminal application between other terminal applications.
- crabbone 3y ago
  > Don't surprise me. How's this a "research"? It's just about you, your attitude, your lack of experience with computers... Why should anyone take seriously claims coming from someone who didn't even bother to learn to use the thing they claim to have bad user experience?

p-e-w 3y ago

> I'm curious about what "decades of UX research" improvements you are talking about Here's the most important one of them: Don't surprise me. Blend in. Look and behave like other programs. There are 50 applications on my system. Yours is one of them. If all other applications use 'Ctrl+C' for copying text, but your application uses 'y', then your application is the problem.

spoonfeeder006 3y ago
Thats a basic principle. But when you say decades of UX research you imply actual new ways of doing things And something innovative and effective would be both self explanatory and actually useful, so it ultimately gets adopted by others instead of simply surprising and confusing people
akho 3y ago
But Nyxt (which is modeled on Emacs, not Vim) would blend in for me. I spend most of my time in Emacs and Firefox; I would prefer a browser that blends in. I don’t know about 50 applications. The rest of the applications I use are more specialized, and have their own shortcut madness. Browsers ate most of the small stuff.
gsinclair 3y ago
That would be a problem if vim was installed front and centre on everybody’s computer and they were all expected to use it. That is not the case. You choose to use it, so you either accept, or better yet, embrace that y=copy, or you choose to use something else. Trying to objectively describe vim as a problem by invoking UX research is very funny. The end result of that logic is to rule out modal editors altogether.
8organicbits 3y ago
What are you talking about? I suspect you haven't used vim recently. In the context of the command line Ctrl+C sends SIGINT, which usually interrupts/terminates a program. When I press Ctrl+C, vim shows "Type :qa and press <Enter> to exit Vim". All my command line programs handle it as SIGINT. Imposing Ctrl+C as copy would be inconsistent and surprising. If I'm using Visual Studio with vim keybindings Ctrl+C/Ctrl+V are still copy/paste (I suspect this is because VS provides this and the keybindings don't override it). I think every other editor with vim keybindings I've used preserves this behavior. Ctrl-C as copy is consistent with every other windowed program I'm running. Where have you encountered vim keybindings that don't permit this?
xigoi 3y ago
Vi is several years older than the Ctrl+C shortcut for copy. How could it possibly have know that Ctrl+C would become a more popular choice for copying?
usrbinbash 3y ago
> Don't surprise me. Blend in. Look and behave like other programs. There is hardly anything in the world that blends in better with everythign else, then a terminal application between other terminal applications.
crabbone 3y ago
> Don't surprise me. How's this a "research"? It's just about you, your attitude, your lack of experience with computers... Why should anyone take seriously claims coming from someone who didn't even bother to learn to use the thing they claim to have bad user experience?