I honestly can't tell if this is sarcastic or not. I've been typing `curl -O http: ...` into command prompts for decades, and that Powershell incantation looks awfully unwieldy.
In what way is it the happy path?
I honestly can't tell if this is sarcastic or not. I've been typing `curl -O http: ...` into command prompts for decades, and that Powershell incantation looks awfully unwieldy.
In what way is it the happy path?
People for some reason always show long stuff that is only used when you write scripts to share with others and not interactivelly - you could do the same with curl if you use --long-parameter-names but somehow people are biased when talking about posh like aliases and other things do not exist.
Invoke-WebRequest is just iwr
No, you should always use it.
Its maybe a problem when ultimate performance is in question, but you can go long way with Powershell - I recently had a web service SOAP client implemented in it that did millions of requests in an hour using threads in less then 50 lines of code consuming less then 3% of server resources (running entire country in single day actually)
> I end up just using WSL ubuntu
You can have basiclly anthing working without WSL (except maybe docker correctly).
> Also I don't really know the commands so it feels crippled to me (no ssh (still? idk),
SSH is there. Learn commands along the way. You should def take a book like this one: https://www.manning.com/books/learn-windows-powershell-in-a-...
> not many tools,
All usual tools, linux and windows, can be used. You have majority of them hosted on chocolatey.