5 ms·

Hey, you are assuming that a touch typer that doesn't look at the keyboard often because she doesn't receive more information when she looks down will not find

Hey, you are assuming that a touch typer that doesn't look at the keyboard often because she doesn't receive more information when she looks down will not find information that is useful when it is indeed shown at the keyboard, because she doesn't look for it. It is a circular and flawed argument; most probably, a change of functionality of the tool will produce a change of workflow. You are also not considering: - you aren't either touch typer or not; it is a continuum where people look at the keyboard with decreasing frequency through time - being a touchtyper is a multidimensional activity; on top of the muscle memory of each letter there is the muscle memory of the semantics. You might not know specific emacs chords even when being a touch typer; in this example, having information displayed would be valuable.

diffeomorphism 8y ago
> Hey, you That sounds rude... I am assuming that a "touch typer" has her fingers on the keyboard most of the time, usually on the home row. In particular, her hands will be covering most of the keyboard. Also, even if the keyboard shows something interesting, always switching your view up- and downwards is bad ergonomics and context-switching. Thus showing that information on the screen like which-key is more useful than having to lift up your hands, read what is written on your keyboard, put you hands down again, press the now covered keys.
- harperlee 8y ago
  > That sounds rude... Sorry, I did not realise this sounded rude, not my native language. In what sense does it sound rude? Too informal? Too confrontational?
- harperlee 8y ago
  > a "touch typer" has her fingers on the keyboard most of the time, usually on the home row Sure - until you need contextual help directly mapped to the actions you need to do. Then it’s just a matter of looking down. It cannot get a lot more intuitive than looking where to press if you don’t know it by heart, right? It is what we already do to learn where the letters and special characters are - just providing a higher level of meaning to the keys.

diffeomorphism 8y ago

> Hey, you That sounds rude... I am assuming that a "touch typer" has her fingers on the keyboard most of the time, usually on the home row. In particular, her hands will be covering most of the keyboard. Also, even if the keyboard shows something interesting, always switching your view up- and downwards is bad ergonomics and context-switching. Thus showing that information on the screen like which-key is more useful than having to lift up your hands, read what is written on your keyboard, put you hands down again, press the now covered keys.

harperlee 8y ago
> That sounds rude... Sorry, I did not realise this sounded rude, not my native language. In what sense does it sound rude? Too informal? Too confrontational?
harperlee 8y ago
> a "touch typer" has her fingers on the keyboard most of the time, usually on the home row Sure - until you need contextual help directly mapped to the actions you need to do. Then it’s just a matter of looking down. It cannot get a lot more intuitive than looking where to press if you don’t know it by heart, right? It is what we already do to learn where the letters and special characters are - just providing a higher level of meaning to the keys.