It's in the list given by author:

apt, ssh, rsync, find, grep, awk, sed, sort, xargs, md5sum, gpg, curl, wget, apache, mysql, python, perl, ruby, php, gcc, tar, vim, emacs, diff, patch...

At least half of these already exist, either as .NET cmdlets, Command Prompt functions, or Windows EXEs.

RDP, Robocopy, Find.exe, Sort-Object, Select-Object, Select-String, Invoke-WebRequest, Invoke-RESTMethod, IIS, .NET, CMD, ASP.NET, and Compare-Object will fill most of those needs.

And Powershell accepts "cat" if "gc" for "Get-Content" is too long. Or "ls" if "dir" or "gci" for "Get-ChildItem" is too long. And each of these is a case-insensitive object you can pipe right into ConvertTo-Html or Send-MailMessage.

Or you can create a UDP socket with .NET right from Powershell, and send your objects that way.

It's already working as shown in the video demo: https://channel9.msdn.com/Events/Build/2016/P488

It works really well in Powershell. I use it on Win8.

https://juliankay.com/development/setting-up-vim-to-work-wit...

Presumably, as it's not a GUI application. Not gvim though.

You can already run vim from the msys git distribution

There is also a native Vim, compiled with Visual Studio: http://tuxproject.de/projects/vim