4 ms·
True, but no matter the terminal, you still have to deal with either cmd or PowerShell (and its horrendous startup time), "active code pages", and the fact that
by Longhanks 2y ago
True, but no matter the terminal, you still have to deal with either cmd or PowerShell (and its horrendous startup time), "active code pages", and the fact that you cannot write UTF-8 to stdout without it getting messy - you need WriteConsoleW and/or SetConsoleOutputCP but that affects the whole environment, ... cli on Windows was and is painful.
- pjmlp 2y agoPowerShell 7.4.2 starts in 1s for me.
- Longhanks 2y agozsh starts in 0.1s for me. 1000ms is a very noticable latency to me...
- pjmlp 2y agoImagine how much work we would do with those additional ms per day.
- radonek 2y agoOnce upon a time, I was tasked to rewrite build scripts for windows based team from .bat files to bash scripts (via a git-bash). People on that team were not exactly unix fans, in fact they resisted hard almost everything coming from us linux weirdos. But reduction in build time was so big they asked for this and embraced it with genuine love.
- pjmlp 2y agoI bet it was a bit more than a few ms per day.
- zubairshaik 2y agoYou can run WSL or nushell on Windows Terminal