3 ms·

It is crazy, I agree. But you have to keep in mind how old this protocol is. Layers and layers of cruft which you can trace back to before the computing era. He

• TheCondor 5y ago
  No question, it cuts deep and we would/should look at it end to end. A big part of it is all the tty/pty black magic that we’ve just built on top of. It’s a gigantic task, but when I see new folks reimplementing “ls” as a “modern replacement” and I do find value with many of these tools (I love ripgrep and bat, among others) I hope/wish someone felt the itch to tackle this.
• dr_zoidberg 5y ago
  > Layers and layers of cruft which you can trace back to before the computing era. Even those layers and layers don't _have to_ slow things down. Check the refterm "debacle" ([2] for the context, [0, 1] as Muratori's answer to it). It's just the way things are usually programmed doesn't care about performance and how fast things really can be. I sometimes wonder in we're not due for a massive round of optimization on a couple of the layers that we're used to using/depend on. [0] https://www.youtube.com/watch?v=hxM8QmyZXtg https://www.youtube.com/watch?v=hxM8QmyZXtg [1] https://www.youtube.com/watch?v=99dKzubvpKE https://www.youtube.com/watch?v=99dKzubvpKE [2] https://github.com/microsoft/terminal/issues/10362 https://github.com/microsoft/terminal/issues/10362