Skip to main content

Unknown parent

daniel:// stenberg://

@notmybackdoorbug powershell on Windows still has a curl alias that is not curl. Windows also ships curl.exe that is the real curl.

Not confusing at all!

in reply to daniel:// stenberg://

I wonder if you could do it their way instead. Trademark and Cease&desist ๐Ÿคช
in reply to daniel:// stenberg://

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.
Unknown parent

in reply to daniel:// stenberg://

@shaknais from curl's point of view, I expect that the better solution is to ship it as "actually_curl", highlighting to Windows users that "actually_curl" is the actual curl and that other curls installed on their system is not.
in reply to daniel:// stenberg://

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.
in reply to daniel:// stenberg://

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.
โ‡ง