Typing inside of the default WSL terminal feels amazing (2018)

Post by gdy » Mon, Dec 23, 2019, 5:50 PM UTC

ohthehugemanate wrote: post #33

swiley wrote: post #23

Earlier quoted context omitted.

I would be shocked if it were faster.

Depends on the operation in question. Direct syscalls should be faster, but there are some big differences between the NT and Linux kernels. You end up getting all the poor performance areas of BOTH. That, and HyperV has an extremely fast lightweight VM mode for particular hardware. For example, running containers on HyperV actually runs them with VM level isolation, a la Kata containers... and at competitive speeds.…

Post by japhyr » Mon, Dec 23, 2019, 5:52 PM UTC

nickjj wrote: post #89

rwerkjlkjweq wrote: post #86

Earlier quoted context omitted.

Can you post your computer specs? Because it's impossible for me to see any difference between the WSL terminal and Notepad. I can see a tiny difference compared with Electron apps, but I really need to concentrate to see it. My computer is no rocket, is a higher-end desktop from 6 years ago.

Mine is a ~6 year old i5 quad core desktop. A complete list of hardware can be found here: https://nickjanetakis.com/blog/the-tools-i-use#computer-desk... If you can't notice it much, perhaps your monitor has really bad input lag and it's overtaking any difference between terminals. My monitor has very low input lag (about 13ms) but most monitors have 50-60ms or worse. There's another comment in this thread where I g…

Post by 1996 » Mon, Dec 23, 2019, 6:00 PM UTC

est31 wrote: post #53

nickjj wrote: post #37

Earlier quoted context omitted.

Alacritty has kind of a lot of input latency, it's noticeably worse than wsltty and the default WSL terminal -- at least back when I checked it a year ago. I think some work has been done to improve it, but at this point IMO if you're on Windows then wsltty is as good as it gets for a general purpose terminal. If you're on Linux, xterm is top notch.

What's top notch on Wayland?

Post by zamadatix » Mon, Dec 23, 2019, 6:11 PM UTC

DHowett wrote: post #80

meatcar wrote: post #76

Earlier quoted context omitted.

I just want to emphasize that wsltty is the only well-behaving terminal currently available for WSL. It's the only one that supports mouse interaction in a terminal like scrolling/resizing panes in tmux/vim, unlike any Microsoft solution. If you're using WSL on a regular basis, I highly recommend it. Its a huge quality-of-life improvement.

I am fairly certain that the inbox console host supports mouse interaction (with WSL and anything else that uses VT mouse mode). As the engineering lead for the console and terminal projects, though, I’d love to know how else we can improve!

Post by cjbprime » Mon, Dec 23, 2019, 7:26 PM UTC

joshspankit wrote: post #74

nickjj wrote: post #36

Author of the GitHub issue here. I was surprised to see this title, because I thought "holy cow, finally someone else appreciates low input latency" and then I realized it was my issue haha. By the way, wsltty 3.x also has excellent input latency now too. I've been using it for quite a while now with terminal Vim in WSL and it's about 90% as good as xterm on native Linux in terms of latency. wsltty also has no issues…

Another vote for low-latency here. It’s tempting to create a YouTube channel dedicated to showing input latencies for common tasks. Question is: how do you make sure no one is cheating?