[laxis96]

Because Windows does not have a good SSH implementation and PuTTY has always worked extremely well for me as a serial and SSH terminal (also, it starts up instantly and never crashed on me).

Are there any better alternatives?

[janosdebugs]

Doesn't Windows ship OpenSSH these days?

[commandar]

It does. I use Windows Terminal and the native OpenSSH client literally daily.

[soco]

I like having a library of hosts to choose and maybe multiple tabs in one place, and although there are some slightly less cumbersome PuTTY frontends like KiTTY (please keep your expectations very very low), I'll rather use WinSCP (no quantum leap in usability either). Edit: to those suggesting W10 command line - yes it's there and works, but it's just that, a command line, not much help when you have dozens of servers.

[nolongerthere]

Windows 10 natively supports SSH as far as I can tell, I don’t use it a ton, but haven’t had any issues just typing ssh username@domain

[n_plus_1_acc]

Many people I know just use SSH from the WSL CLI.

[ale42]

You can run SSH from a Windows terminal without even having the WSL installed...

[CoolCold]

I do like 99% of the time and in quite specific cases from the host machine (Windows native openssh) - mainly due to my environment is in WSL in terms of dotfiles, cmd line prompt, shell history and so on.

[xorcist]

That's a very limited terminal in terms of capabilities.

Then there's things like x11-style copy-paste.

[LoganDark]

PuTTY is from before WSL, and old habits die hard.

[mldbk]

I used to use KiTTY, because it is more versatile.