3 ms·

> (I'm guessing the author means VS Code, not MS Word here?) I took that to mean that the author painted all non-emacs editors as not really being useful edito

• shakow 4y ago
  That's not reading between the lines, that's just inventing a new article.
  • IncRnd 4y ago
    I'm pretty sure it was a fair reading, for people who read the article. The article discussed the option of throwing 40 years of development out the window or borrowing/imitating things from emacs/vim. Then the MS Word comment was made, "It never ceases to amaze me that MS Word and its ilk do not seem to have equivalents of ..."
    • shakow 4y ago
      I'm pretty sure you are reading what you want to tread instead of what is written. > The article discussed the option of throwing 40 years of development out the window or borrowing/imitating things from emacs/vim. The article says that even in a 40 y.o. piece of software such as emacs, low-hanging fruits can be found; and thus, that people writing new editors should take inspiration from features from vim/emacs when creating their own, and stand on the shoulders of 40 years of incremental improvements. Then, as an aside, he remarks that he's surprised that MS Word has not borrowed the lossage feature from emacs – with which I agree: when I accidentally hit keys and break a document, it would be useful to know which key I hit, and which functions I triggered.
      • deleted 4y ago
        [deleted]