5 ms·

As someone who just started working as a developer and is using windows for the first time in 4.5 years, I can't believe how much I miss ssh and command line to

As someone who just started working as a developer and is using windows for the first time in 4.5 years, I can't believe how much I miss ssh and command line tools for everything... ssh keys would solve so much trouble with scripting and credentials... Also sudo...

adventured 8y ago
As a developer do you have to use the Windows GUI or can you use eg the Ubuntu Windows Subsystem for Linux? I highly recommend it. https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
- shaklee3 8y ago
  Seconded. WSL on Windows 10 has a basic ubuntu CLI install that you can run any CLI program on it works great.
_hao 8y ago
As other comments mentioned, just use the Linux sub-system + I would add Cmder as an alternative to the horrible native console. Edit: Cmder - http://cmder.net/ http://cmder.net/
- Jaruzel 8y ago
  I have zero issues with the native cmd.exe. However, I have changed the following: * Set the default font to Droid Sans Mono (Slashed) [1] * Set the scroll back to 9000 lines, and the default width/height to 132x50. * Used ANSI to colour code the prompt. * created a small tool called su.exe that re-launches cmd.exe as Administrator (it can't be done inline unfortunately) And then I use openSSH (the Windows 10 bundled version) to remote to linux boxes. It's all fine. I really don't understand the hate. --- [1] my own edited copy of Droid Sans Mono where the Zero has a 'slash' added.
  - mixmastamyk 8y ago
    Sure with a half dozen fixes you get an approximation of a modern terminal. GP is talking about the console, not the shell however. The console is a character grid designed around VGA hardware, not built on streams as a proper terminal is. CMD is another horribly-designed feeble tool compatible with COMMAND.COM, acceptable back in the eighties. Yes, its fine for running a program or two here and there if you've got low expectations. You can get work done on 640x480 too, but we don't suffer that today. ;-) I recommend this series of posts that will explain how poor the situation has been on Windows, and how it is improving: https://blogs.msdn.microsoft.com/commandline/2018/06/20/windows-command-line-backgrounder/ https://blogs.msdn.microsoft.com/commandline/2018/06/20/wind...
    - Jaruzel 8y ago
      Thanks for that, I'll have a read.
com2kid 8y ago
From a developer perspective, Windows does SSH keys just fine. You can't SSH into Windows boxes (yet apparently!) but you can SSH out of them a-ok. Window Key, type "optional features" and install the OpenSSH client.
- emit_time 8y ago
  Yeah... that's the thing. We're a windows shop 100%. So it's non trivial controlling other machines from a command line. I miss it so much.

adventured 8y ago

As a developer do you have to use the Windows GUI or can you use eg the Ubuntu Windows Subsystem for Linux? I highly recommend it. https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux

shaklee3 8y ago
Seconded. WSL on Windows 10 has a basic ubuntu CLI install that you can run any CLI program on it works great.

_hao 8y ago

As other comments mentioned, just use the Linux sub-system + I would add Cmder as an alternative to the horrible native console. Edit: Cmder - http://cmder.net/ http://cmder.net/

Jaruzel 8y ago
I have zero issues with the native cmd.exe. However, I have changed the following: * Set the default font to Droid Sans Mono (Slashed) [1] * Set the scroll back to 9000 lines, and the default width/height to 132x50. * Used ANSI to colour code the prompt. * created a small tool called su.exe that re-launches cmd.exe as Administrator (it can't be done inline unfortunately) And then I use openSSH (the Windows 10 bundled version) to remote to linux boxes. It's all fine. I really don't understand the hate. --- [1] my own edited copy of Droid Sans Mono where the Zero has a 'slash' added.
- mixmastamyk 8y ago
  Sure with a half dozen fixes you get an approximation of a modern terminal. GP is talking about the console, not the shell however. The console is a character grid designed around VGA hardware, not built on streams as a proper terminal is. CMD is another horribly-designed feeble tool compatible with COMMAND.COM, acceptable back in the eighties. Yes, its fine for running a program or two here and there if you've got low expectations. You can get work done on 640x480 too, but we don't suffer that today. ;-) I recommend this series of posts that will explain how poor the situation has been on Windows, and how it is improving: https://blogs.msdn.microsoft.com/commandline/2018/06/20/windows-command-line-backgrounder/ https://blogs.msdn.microsoft.com/commandline/2018/06/20/wind...
  - Jaruzel 8y ago
    Thanks for that, I'll have a read.

com2kid 8y ago

From a developer perspective, Windows does SSH keys just fine. You can't SSH into Windows boxes (yet apparently!) but you can SSH out of them a-ok. Window Key, type "optional features" and install the OpenSSH client.

emit_time 8y ago
Yeah... that's the thing. We're a windows shop 100%. So it's non trivial controlling other machines from a command line. I miss it so much.