You’ve just triggered my fight or flight reflex. Three years ago I spent about three months writing an entire .NET/WPF application with nothing but Powershell and XAML. Having access to .NET was nice… but the shell was trying to be too many things at once and the mix of method calls, programs, and cmdlets was infuriating.
I’ll never forgive them for aliasing curl to Invoke-WebRequest instead of the real curl.exe.
![[Plasma] Defaults with a bit of tweaks](https://lemmy.everypizza.im/pictrs/image/c1e8b153-5eba-4fb9-9faa-6b76e3d43295.png){kind=link}
it works well, is fast, and a powershell script this one makes can work on Windows pretty easily
You’ve just triggered my fight or flight reflex. Three years ago I spent about three months writing an entire .NET/WPF application with nothing but Powershell and XAML. Having access to .NET was nice… but the shell was trying to be too many things at once and the mix of method calls, programs, and cmdlets was infuriating.
I’ll never forgive them for aliasing
curltoInvoke-WebRequestinstead of the realcurl.exe.At least they walked that one back, by just shipping curl with Windows.
They did in version 7, but not in version 5, and even Windows 11 only bundles 5. All the bullshit aliases are still there.
True, they removed the aliases in Core, but left them alone in the bundled version since much like base
cmdthey’re not updating it anymore.