If you are talking about typing, then I agree, 100ms lag after every keystroke, would be noticeable and annoying, but edits?
Surely you are not claiming to be doing 10 edits a second, where you might need to start complaining about 100ms lag?
I'm not really sure how you've interpreted my claim but the context of this discussion was about holding the text as an unbuffered array. This would mean every keystroke is effectively an edit. But even that aside, I'm sure we've all done stuff like:
type "foobar\n" -> select "foobar\n" -> copy
ctrl+v
ctrl+v
ctrl+v
ctrl+v
ctrl+v
...or the equivalent with replacing text within blocks of the same document; or other repetitive textual tasks that could easily be marcoed if it were a job you'd need to repeat again at a future point in time.
Yes, but that was 50 years ago(!!!) and technology + expectations have moved on considerably since then; which that article explores. Thus my take away from that article is that 100ms is very perceivable and thus simply not fast enough for some applications.
For what it's worth, the article correlates with my own personal anecdote as well.
Going back to the original point, 100ms might still be good enough for a text editor, generally speaking. But going back to my own anecdote, I do find it highly frustrating when running into lag on a text editor when I'm banging out quick edits when either in the zone or working to a tight deadline. Frustrating enough that I have stopped using some text editors because of it.