On the topic of ssh/dealing with other computers, doesn't PuTTY do that pretty well on windows? Though I may be misunderstanding the advantage you're pointing out.
I used to use Putty for all my SSH on windows, until I discovered mobaXterm; it's Fk amazing. not only an SSH client, but you can also browse files at destination, and copy files there from same window; it also has xserver built in to run GUI on destination machine
True, could not get used with putty myself also. But since I upgraded to Ubuntu I started using only PacManager as my primary ssh connection manager and never looked back
Back in the late 90's I used to carry a memory stick with VNC and putty upon that I use to tunnel a VNC connection over SSH to my home network and oven over bonded ISDN (128k which I had at the time in the UK) it was more than usable or attaching to any of my systems.
Then Cygwin came of age, proved very very very useful for adding the tools windows corporate desktops missed out upon for work related activities.
But in all that time, PuTTy has been a very good terminal client for SSH needs. Whilst it is good that Microsoft is adding this, it has never been a hurdle for many and those who run into a corporate wall that tough, have always been able (from the ones I've worked with and collegues) been able to circumnavigate around it :-
Usually using the corporate security policies to bash the corporate desktop witch upon the head. Fight fire with fire if you can't bend the rules.
I only ever used one-the SSH client. It was far nicer than PUTTY for those occasions where I needed to SSH from windows. Maybe I'll just do it from Termux on my phone from now on.
You may be interested in MobaXterm. Don't let the name fool you; it's a good SSH client for Windows. I spent 20 years or so hassling with PuTTY, and just discovered this a few months ago. More people should know about it. I still need pagent for git, and the like, but at least Moba solves the set-the-terminal-options-once-for-all-SSH-sessions problem.
Putty is just a ssh client. Terminal is a shell that has access to ssh so you can access your own files or redirect ports easily through a remote ssh session(you can do this with putty but you must go through some hoops, ie. loopback device and setting up some ports in the putty config), etc.... I love the tabbed terminals that terminal provides. I can ssh into a work computer and have my local shell in another tab. Very seamless.
I have only ever used X over ssh, at least as far as running applications remotely. Particularly when I'm on a windows box - putty + Xming is fantastic.
Note that although PuTTY has a graphical user interface, it is hardly user friendly. Using the command-line ssh (with a decent shell) is much more comfortable.
I've been doing the same with Guix. However, more so lately with declarative, lightweight VMs. It's nice to be able to painlessly make throw away environments that I can easily log into via SSH.
I don't know what I'd do without being able to ssh into VM instances. Whether it's for looking at various logs, the occasional core dump, or uploading a custom binary to test something, it's incredibly time saving.
Can anyone comment to how nice or awful running some sort of Linux VM (maybe under Hyper-V) and using Putty to SSH to it for development on Windows would be? This work is promising, but doesn't appear "quite there", yet. I run OSX now, but don't really ever develop directly on the machine and am mostly SSH'ed to Linux hosts for development.
Putty allowed for more secure remote working when on untrusted networks, but not having to constantly enter credentials is much more preferable.
reply