3 ms·
>Modern text editors have higher latency than 42-year-old Emacs. Text editors! What can be simpler? On each keystroke, all you have to do is update a tiny recta
by coldtea 7y ago
>Modern text editors have higher latency than 42-year-old Emacs. Text editors! What can be simpler? On each keystroke, all you have to do is update a tiny rectangular region and modern text editors can’t do that in 16ms. It’s a lot of time. A LOT. A 3D game can fill the whole screen with hundreds of thousands (!!!) of polygons in the same 16ms and also process input, recalculate the world and dynamically load/unload resources. How come?
Well, where's your word processor buddy? Try to write one to achieve those goals -- and offer what people want today, including syntax highlighting, linting, auto-completions, etc, and come back to us...
- anthk 7y ago>Well, where's your word processor buddy? Try to write one to achieve those goals -- and offer what people want today, including syntax highlighting, linting, auto-completions, etc, and come back to us... Emacs could do that since 25 years ago, if not more.
- coldtea 7y agoEmacs never could, and still can't draw while processing input, and even needs occasional manual refresh. A badly written code (plugin, etc), a loaded loop, etc, can freeze emacs. So there's that... And, Lisps aside, the kind of linting, auto-completion, understanding of syntax/AST, etc emacs could do 25 years ago is much easier compared to what devs expect today.
- zamadatix 7y agoGvim and Sublime do this quite well. I haven't looked at the Xi editor mentioned in the article but I would assume it does a decent job or it wouldn't have been mentioned. VScode actually isn't even that bad considering it's Electron based but doesn't quite meet the mark. Also you're conflating syntax highlighting/auto-competition with time to render an update to an input. You don't need the popout letting you know that 17 source files and 50k lines over it found "TextComplete()" is a valid auto-complete and should be turned blue in order to draw an "x" to the screen in response to a keystroke.