Exactly eight years ago #Microsoft made powershell open source and I *immediately* filed a pull request to remove their #curl alias...

Did not really work.

https://daniel.haxx.se/blog/2016/08/19/removing-the-powershell-curl-alias/

Removing the PowerShell curl alias?

PowerShell is a spiced up command line shell made by Microsoft. According to some people, it is a really useful and good shell alternative. Already a long time ago, we got bug reports from confused users who couldn't use curl from their PowerShell prompts and it didn't take long until we figured out that Microsoft โ€ฆ Continue reading Removing the PowerShell curl alias? โ†’

daniel.haxx.se
@bagder I wonder if you could do it their way instead. Trademark and Cease&desist ๐Ÿคช
@aquarius that would cost me a fortune in legal fees
@bagder I bet it would... wonder if FSF would be willing to invest to create a precedent... or gofundme. But in the end it's probably better to avoid the bloodshed at all. Thank you for your service to the OSS community.

@aquarius @bagder Compare April 2023, when Rust Foundation announced intent to assert a restrictive trademark policy that would have made bootstrapping tool mrustc illegal. The foundation had to backpedal hard two weeks later.
https://developers.slashdot.org/story/23/04/22/0250212/rust-foundation-apologizes-for-proposed-trademark-changes-promises-improvement

#RustFoundation #trademark #rust

Rust Foundation Apologizes For Proposed Trademark Changes, Promises Improvement - Slashdot

"The Rust Foundation on Monday apologized for confusion caused by the organization's proposed trademark policy changes," reports the Register. The Foundation now says their proposed policy "clearly needs improvement" and "there are many valid critiques of the initial draft," promising to address t...

@bagder How did it end?
@collectifission exactly nothing happened and they still today have the alias
@bagder @collectifission Still present in Windows PowerShell but it have been removed from PowerShell 7.
Powershell crashing System.OutOfMemoryException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand ยท Issue #21443 ยท PowerShell/PowerShell

Prerequisites Write a descriptive title. Make sure you are able to repro it on the latest released version Search the existing issues. Refer to the FAQ. Refer to Differences between Windows PowerSh...

GitHub
@bagder It was asinine to add the aliases without any attempt to handle arguments correctly. It was asinine not to fix it when you pointed it out. It's not like we don't know, as an industry, how to handle breaking changes. You phase them in with increasing warnings until, yes, you break people's scripts. FFS.
@tjcrowdertech yeah, there was just that tiny little thing that was lacking: will

@bagder PowerShell's curl alias for Invoke-WebRequest is such an utterly stupid feature! There was never any need for such an alias.

Luckily curl.exe still invokes the real curl in PowerShell ๐Ÿ˜…

@bagder Maybe in the next coming eight years. But probably not.

@bagder We should all log bugs against powershell for every curl feature that doesn't work right in their "implementation"

They knew full well what they were doing when they added those aliases. They were trying to take advantage of the work of the open source community. It is not helpful. It hurts users.

@bagder That was stressful to read ...
@bagder I know that there are some people at Microsoft who care about open source, fairness, mutual support etc.
I wonder what those people think, e. g., @shanselman, @davidfowl.
Sometimes big enterprises get caught up in business rules and compatibility requirements and forget about common sense and fair interactions between humans but there are always people in there who can see through all this and can escalate things in there.
As curl users we can probably agree that the alias is pointless.
@brar @bagder The alias is also gone, and curl has shipped by default in Windows since Dec of 2017.
@brar @bagder no itโ€™s not a perfect solution but itโ€™s better. I have been - and will continue to - push for the right thing from the inside
@shanselman
It's only gone if users manually update their powershell version, so the majority of people still have it.
@paul @shanselman Itโ€™s likely there are a number of customers who have built on that functionality and it would break things to remove it. I agree it shouldnโ€™t have been aliased by default in the first place in the classic PowerShell.

@rombat @paul @shanselman Then again, the recommendation Iโ€™ve always heard is not to use aliases in scripts as that may potentially break things down the line.

Personally, I have to say I actually prefer the โ€œnewโ€ Microsoft that sometimes breaks things that were bad ideas to start with and would like to see more of that. How long until PS5 is an optional extra you need to `winget install` on the few servers and workstations that demand it while the OS gets current PS by default?

@mikael @rombat @paul ya that default is going away soon I hope, it's VERY classic - it's there for compat
@shanselman The alias appears to still be there using the version of PowerShell that comes with Windows 11 (5.1). I'm guessing I need to manually upgrade to v7?
Installing PowerShell on Windows - PowerShell

Information about installing PowerShell on Windows