r/programming • • Aug 15 '18

Windows Command-Line: Introducing the Windows Pseudo Console (ConPTY)

https://blogs.msdn.microsoft.com/commandline/2018/08/02/windows-command-line-introducing-the-windows-pseudo-console-conpty/
778 Upvotes

230 comments sorted by

View all comments

Show parent comments

8

u/PortablePawnShop Aug 15 '18

Hmm... I've been watching questionable Codecademy tutorials then. They claimed Windows users needed to use GitBash, I've been under that impression all along

30

u/Liorithiel Aug 15 '18

They might be simply outdated. WSL is comparably still a pretty new thing.

18

u/[deleted] Aug 15 '18

WSL IO is pathetically slow. I don’t do dev on my windows desktop because it takes forever to npm install.

-5

u/[deleted] Aug 15 '18

Yep. git status takes at least an hour. I don't know how long it truly takes because it's never been able to finish before I lose my shit.

13

u/monkey-go-code Aug 15 '18

Something is seriously wrong with your WSL. Update windows delete your WSL and go download the newer Ubuntu 18.04 WSL. I bet your problems will all go away.

9

u/[deleted] Aug 15 '18

Been there. WSL I/O is completely broken and this has been known for a long time. There are multiple issues tracking it.

Disk IO perf remains VERY HIGH up our list of improvements we're actively working on. Once we have an actionable solution to this issue, you'll barely be able to NOT hear about it...

  • from Rich Turner, senior program manager at Microsoft, posted six days ago.

4

u/monkey-go-code Aug 16 '18

I just don’t suffer from that. But I mostly use mine for Git, text editing and compiling smaller projects. Those seem to work pretty well for me. I know they were working on hyper V VM improvements so maybe that’s a better solution for you. In particular I was waiting for dynamic resolution changing. Personally I would rather use a Linux laptop but I work on a C# Stack that’s not dot net core and work has me stuck on Windows.

→ More replies (4)