`curl | sh`, take 2:) I hope nobody would be impressed, unless there's some safety features that aren't obvious here.

FYI powershell comes with curl now (and ssh).

I'm aware of openssh on NT being a thing now, but last I saw I thought powershell's "curl" was just an alias to their equivalent, which means that ex. options don't actually match for anything non-trivial. (IIRC, they did this with lots of commands; `ls` gets mapped to a local equivalent, but `ls -lahr *.foo` would not do what you think it should)

It's the real curl[0]. I actually like the aliases and they've even added ctrl-shift paste in the options. Maybe they should be the default.

The windows filesystem still makes no sense but that's an NT issue (dropbox cant sync con.sh???). SSH has a surprisingly native feel but graphical apps (vim, screen) still have rendering problems, and the ssh-agent daemon isn't set up right by default.

Until they make Windows LTSC unusable, it's not _too_ horrible right now. But for a serious programming project there's still no question for me (but fix your damnable sound drivers Ubuntu).

[0] https://blogs.msdn.microsoft.com/commandline/2018/01/18/tar-...

You can download/run the powershell script separately.

When you do it from a non-admin powershell, it's precisely as secure as downloading and running an installer.