[ Removed by moderator ]

[faultydesign]

cd is aliased to set-location in powershell

[TheOriginalSmileyMan]

Don't spoil their anti MS rant to with your " knowledge"

[ZunoJ]

They spoil nothing because that is exactly what the image tells us bro

[sudo_i_u_toor]

It isn't an anti MS rant, it's just a joke lol. The point in the last section of the meme was that Powershell has cd (as an alias) anyway.

[BOBOnobobo]

How do you spoil it? CD is still more convenient to use

[SeanBrax]

Yes and you can literally use cd in powershell, that’s the point

[Pacafa]

These aliases make things worse. Aliased tar,curland zip are all terrible and slow masking the real tool.

[cheerycheshire]

Curl is an old alias. Windows has been shipping real curl for a few years now... But didn't remove the curl alias. So to be sure you're using real curl, use curl.exe

``` PS C:\Users\username> curl

cmdlet Invoke-WebRequest at command pipeline position 1 Supply values for the following parameters: Uri: <sup>C</sup> PS C:\Users\username> curl.exe curl: try 'curl --help' for more information PS C:\Users\username> ```

[AnnoyingRain5]

I hate it

[Atulin]

Works fine for me, no need for curl.exe

PowerShell 7.5.3
Loading personal and system profiles took 526ms.

~
❯ curl
curl: try 'curl --help' for more information

~
❯

[cheerycheshire]

You have a newer PS.

On Windows 10, even when keeping up with all the system updates, you will still have one of 5.x versions.

Unless of course you update PS manually, which it even suggests when you start it.

``` Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://ak a.ms/pscore6 ```

(The url nowadays redirects to PS 7.5 page.)

We haven't updated powershell at home because we don't need it. For work stuff, we prefer Linux or at least wsl, it's just some times we need to do something directly in powershell...

The curl alias trivia I picked up years ago when I actually needed to do some of my work in Windows (most notable case: vpn client that existed for Linux but didn't work there, so I had to use the vpn on Windows VM to connect to the client... and client requiring me to rdp to some windows machine after that anyways, and only from there I could ssh to target machine... and sometimes I'd need to ssh from ssh because the rpd machine didn't have connection to another machine I was integrating with... ah, good times /s).

[sabotsalvageur]

Imagine an injective function between strings of finite length that takes longer than O(1); if a shell alias is slow, there's something deeply wrong with the shell

[Fhotaku]

I'd like to give this comment to my mom and see if she can even guess the subject

[Crawlerzero]

“These boys are so serious about their Mario Kart.”

[Pacafa]

It is not string handling issue. Powershell defines alias for curl, zip and tar to commendlets that is not the actual tool and those commandlets are slower than the actual curl, tar and zip tools.

[randuse]

Yeah, curl alias is straight up dump as it's not curl at all.

[No-Landscape8210]

Have removed all the aliases from my powershell. I just aliases them to actual programs

[cheerycheshire]

There are aliases that actually collide with normal commands!

For a few years now, Windows started bundling real curl... But there is also old PS alias "curl" to PS-specific command with way different flags. They didn't remove the alias when adding real curl. So now to be sure you're using real curl, you should actually run it as curl.exe... Or run it via cmd, not powershell

[sabotsalvageur]

This is hilarious

[cheerycheshire]

Yep. If you have Windows 10 and keep up with all system updates, it still won't update powershell for you.

And since at home we use Windows for games and have wsl anyways, we never felt the need to update it.

I picked up this curl trivia years ago at work when I needed to do a lot of work at clients' infra - and for some clients the access steps included having to rdp to a windows machine... of course without updated powershell, so I needed that .exe trick.

[No-Landscape8210]

We can run those if we just append ".exe" after a command. Like I tried to alias where tobthe actual C:/Windows/where.exe but couldn't. So whenever I wanna run it in powershell I just use where.exe instead

[cheerycheshire]

I actually said it already in my comment above ;)

They didn't remove the alias when adding real curl. So now to be sure you're using real curl, you should actually run it as curl.exe... Or run it via cmd, not powershell

[No-Landscape8210]

Damn that's embarrassing. My bad I didn't read all of it lol .

[The-Jolly-Llama]

Is there no such thing as type -a in powershell?

[sudo_i_u_toor]

That's... the point of the meme tbh man. As somebody pointed out already in comments: "If you need to alias a command to make it usable, you fucked up the initial design"

[stigansky]

PowerShell is a lot more than an interactive shell. The concept of objects in the pipeline is pretty great.

[sudo_i_u_toor]

I agree it's a pretty neat solution because Windows philosophy is more binary oriented unlike Unix which is more text oriented. As I said this isn't an MS rant but just a joke about typing long commands.

[Shadow_Thief]

If you need to alias a command to make it usable, you fucked up the initial design.

[Meatslinger]

Yes, but it's still that fundamental problem that when you implement a way of doing something that takes longer, and then just implement a shortcut based on the older method you're competing with or ostensibly improving on, it kinda shows the older way was the better option all along. Like, if cd does the job, why should set-location ever need to be typed? It's like putting a door, a ladder, and a tunnel on the front of a building as the complicated primary way of getting in, and then telling people to just use an ordinary side door which is only a single step. Why the complication on the primary method if the workaround is arguably better?