3 ms·
I know many don't care about that but I care about one thing: input latency / lag. There have been many frontpage posts on HN about the subject of latency / inp
by TacticalCoder 3y ago
I know many don't care about that but I care about one thing: input latency / lag. There have been many frontpage posts on HN about the subject of latency / input lag (including when it comes to terminals) over the years.
I've got a CPU doing billions and billions cycles per second and a badass monitor. I want my prompt to feel instantaneous.
And although I'm a big Emacs user and although Emacs is nowadays one of the fastest editor [1] out there (compared to IDEs like VS Code / IntelliJ or any Electron app), I don't feel like any of ansi-term / eshell / libvterm solution feels low latency / no input lag.
That's why although you can pry Emacs from my cold dead hands, I still use terminal emulators outside of Emacs.
I'd say 99.9% of the reason to use a terminal inside Emacs is anyway to cut/paste content from the buffer to Emacs: for that I use a shell script which pipes the output of my command into a new Emacs buffer.
[1] Time it takes to launch Emacs, execute Emacs Lisp code, and exit:
$ time emacs -Q -nw -eval '(kill-emacs)'
real 0m0.049s
49 ms.
- ElectricalUnion 3y agoIt's one of the reasons I really like xterm; besides starting up reasonably fast, actually supporting ANSI escapes and not some random subset of them it had one of the lowest input-to-screen latency ranges of all emulators. - and overall embedding random things like Sixel and tektronics graphic terminal emulation, and correctly handling Unicode and bidi, and supposedly having garbage stdout rendering speed - but I believe if you're dumping several million screenfulls of scrolling text you're holding your terminal wrong.