I don't think I'm alone in considering blinking keyboard cursor/carets as the original sin of this.
Here's an long-running collection of how to disable flashing cursors everywhere, from vi to Vscode: https://jurta.org/en/prog/noblink
> Software development is not an easy task, and often after a painful process of writing a program developers feel they should share their pains with users, so they put a part of own sufferings onto the shoulders of users in a method similar to the Chinese water torture - blinking cursors.
Cursors are fine to me, and frankly important. Flashing is "LOOK HERE IT'S IMPORTANT YOU KNOW WHAT'S HAPPENING HERE" and what happens when I press almost any button is a solid reason for grabbing my attention. I shouldn't have to search in a big pile of thin lines to see the specifically slightly differently shaped thin line to know what's going to happen when I type - let my visual system use the optimised "MOVING" alarms to let me know.
Making me hunt or test where my cursor is by making a change is far worse to me.
Interesting to know that some people find it hard. Does the default behaviour I see while typing (no blinking unless you pause) help?
Here's an long-running collection of how to disable flashing cursors everywhere, from vi to Vscode: https://jurta.org/en/prog/noblink
> Software development is not an easy task, and often after a painful process of writing a program developers feel they should share their pains with users, so they put a part of own sufferings onto the shoulders of users in a method similar to the Chinese water torture - blinking cursors.