Putty, Xshell, SecureCRT, SSH Secure Shell slient which is good?

Now mostly use the Xshell, because Xshell has a personal free, or Chinese interface, for this level four is barely over, really good.
Putty because it is too small, so often a lot of features can not be satisfied.
SecureCRT in function with Xshell (xmanager Chinese version of the site), but SecureCRT is the English version of the charge, so decisively abandoned
SSH Secure Shell slient, this software uses not too much,
The most commonly used is SECURECRT and Xshell, which is a free reason, so it is recommended to use Xshell.

Sister Lou
Links: https://www.zhihu.com/question/25344597/answer/78042407
Source: Know
Copyright belongs to the author.   Commercial reprint please contact the author for authorization, non-commercial reprint please specify the source. Pig Pig
Links: https://www.zhihu.com/question/25344597/answer/46720111
Source: Know
Copyright belongs to the author. Commercial reprint please contact the author for authorization, non-commercial reprint please specify the source.

The Xshell in Xmanager Enterprise suit is the best, no defect. All the others have problems. Other words
Xshell:
1. Color matching is consistent with Linux and also improves the problem that dark blue fonts are not easy to see.
2. Support to enter user name and password from command line on Windows and connect SSH directly, for example: "Xshell.exe-url ssh://Username: password @ip: Port"
3. The form header for each connection can display IP directly, without modifying the Linux system.
4.Xshell has an inverse function: You can write commands in one window, and the name will be executed synchronously in all other windows.

The other:
1.Cygwin: Lack of basic functions, installation and uninstallation are more troublesome, there are cases of damage to the system.
2.Putty: Set the form header for the connection to display IP and need to change the Linux system.
3.SSH Secure Shell: Wrong color.
4.SecureCRT: Wrong color.
5.Mobaxterm: Unable to enter SSH user name and password from command line on win to connect SSH directly.
6.OPENSSH: Unable to enter password. And I forgot where to download the binary package, actually put the system environment variable path to "C:\Program Files (x86) \openssh\bin" (This program ape to append operation mistakenly written as set operation) ... Fortunately, I developed a good habit of testing in the sandbox, or if I measured it directly on the working machine, I would have to reload the computer.

Update: NOTE!
Xshell is not only the best tool for Windows to connect to Linux, but also a good tool for FQ. Buy a VPN abroad, and then in the domestic buy a bypass GFW high-speed abroad line, with Xshell a little configuration can support multi-IP at the same time go abroad.
Test CCIE time, in order to meet the examination room environment, resistance to use putty.
Other time, on Windows with Xshell,mac on Iterm,linux with PAC

Putty, Xshell, SecureCRT, SSH Secure Shell slient which is good?