How is that comment useful? No-one is denying anything. It's obvious that the decision to implement those aliases was incorrect. It's not like Microsoft is saying that it was correct.

It's not a question of who was right or who to blame. It's a question of how to make the changes because there _are_ users that depend on those aliases.

They are also honestly pretty useful as a new user. `ls` and `dir` are more obvious things to try than `Get-ChildItem`.

The half-way solution could have been making the 'aliases' output migration documentation about how to accomplish common takes with the PS commands.

That way PS would be far more discoverable to a UNIX person and would save time searching "$command in powershell".

Yeah but frankly it also sucks to type in such a long command rather than using the aliases.

Most of the commands have PS "native" aliases which also follow a more consistent pattern, e.g., get-childitem->gci, invoke-webrequest->iwr.

That's true, but after years of typing "ls" into terminals that's just more natural.

Then maybe design new ones?

"download" aka "dl" instead of curl/wget?

"list" instead of ls/dir?

Would also make them easier googleable

That's not the problem MS was trying to fix with the Linux aliases -- the problem they were trying to fix was ergonomics. A lot of us are used to Linux commands and are turned off by Windows shells when we have to learn a new set of commands and can't use `ls`.

In fact, being able to do `ls` rather than `dir` on PowerShell was one big reason I gave it a chance. My other Windows shell experiences have been supremely intolerable because of that.

With curl and wget, Microsoft admits they were overeager.

I think the correct ergonomics would be if you saw:

  $ curl http://example.com/foo
  Fetching http://example.com/foo by emulating curl
  This command is an alias for "...".
  If you've installed a real curl command, disable this by typing...

so that you could still use muscle memory to type the commands you know, could see what the actual underlying command is so you could adapt to it, and would know how to use the Real Thing if you have it.

Kind of noisy, isn't it?

It is, but the noise is telling you how it differs from what you'd normally expect and how to address it. I think that's an acceptable tradeoff.

I think it is immediately obvious from the output that it's not the same program, without the message.

Really? What's the normal output? The content of the URL being fetched. If that message was to STDERR so that curl > foo worked without alteration but the help text still showed up on the console, I think fewer people would be surprised.

The number of bugs about this indicates that people are still being surprised.

That is not the output of the PoSh command. Like most of them it outputs a list of object properties and values: https://mcpmag.com/articles/2013/01/22/~/media/ECG/mcpmag/Im...

PowerShell has other ones in addition to the cannibalistic ones. `Get-ChildItem` has `gci` and the command in question, `Invoke-WebRequest` has `iwr` on top of `wget` and `curl`. Admittedly, it's pretty kitchen sinky.

So, there’s already a solution.

Those are not discoverable in the same way.

I think this comment is important in understanding why so much open source software doesn't have backwards compatibility

> If removing these aliases (retroactively, if you want to clean up your act you have to remove this from all versions in which this was ever released) breaks things for some people, then you can go and send people out to help them fix their issues. You knew it was a hostile action, you broke things, you fix them.

retroactively remove things from old versions? This is crazy

No one does that. How is this comment from someone who doesn't understand the "release" concept so important?