4 ms·

> Hmm. They can now have a path to obsolete cmd. As long as they ship a decent ssh client with the system, users will become accustomed to ssh-ing to their own

> Hmm. They can now have a path to obsolete cmd. As long as they ship a decent ssh client with the system, users will become accustomed to ssh-ing to their own box instead of using cmd. Baby steps! SSH is a transport protocol, not a shell. If you SSH to your own box, you're just going to get PowerShell.

jameshart 11y ago
SSH clients are also typically terminal emulators, though. The idea here would be to have an ssh client which acts as a better terminal than cmd.exe does. The effect of this isn't about whether you get access to a better shell, but instead about whether you have a better terminal with which to talk to that shell.
- TylerE 11y ago
  FYI: http://www.hanselman.com/blog/Console2ABetterWindowsCommandPrompt.aspx http://www.hanselman.com/blog/Console2ABetterWindowsCommandP... Will happily run a cmd window, or other command you supply (e.g. I run a cygwin zsh)
  - vickm 11y ago
    I recommend checking out ConsoleZ which is a fork that looks very promising and has a github repo that has more traffic than the sourceforge console2 project.
    - nitrogen 11y ago
      For anyone looking for old and mature options, xterm on a rootless Cygwin X server works quite well.
- gnu8 11y ago
  The definitive SSH client isn't though. PuTTY, SecureCRT and the like are terminal emulators with SSH built in, but those are not the standard. One of the big missing features in Windows is lack of SSH transport. Sure, its terminal emulator is adequate at best, but it does have one. The major news here is that it will finally be possible to remote into a Windows host the same way we remote to everything else.
jevgeni 11y ago
... which is AWESOME.