5 ms·

Very true! When those decisions were made PowerShell was never planned to be run on anything that ran those cmds natively. Now that they have changed the rule

Very true! When those decisions were made PowerShell was never planned to be run on anything that ran those cmds natively. Now that they have changed the rules this should be expected as they move to a more neutral ground. I would be the 1st to call M$ on being jerks, but in this case give them a break the ship just did a 180 if you setup your furniture a certain why I guess you will have to set it up again...deal with it.

warfangle 10y ago
On the other hand, curl.exe has been available for five years.
- doikor 10y ago
  PowerShell was originally designed so that you would mostly just run CmdLets with it so colliding with an actual program wasn't considered an issue. And these aliases haven been available since 2007. They even admitted it them self that it was stupid and needs to be fixed though so just wait I guess? edit: As a separate note I really would like to have versions of curl and wget that actually have all the params working but return the correct PowerShell objects (so the web request result thingie) instead of a String object. Or maybe have it do that with a flag or something.
  - protomyth 10y ago
    I get the feeling there are a lot of commands that are going to need to be customized for actual typed output. It would be an interesting project to do a usr-bin for PowerShell.
- laurent123456 10y ago
  curl on Windows existed many years before PowerShell.
shmel 10y ago
>>PowerShell was never planned to be run on anything that ran those cmds natively. Really? I thought that windows versions (native versions, not even cygwin) of wget and curl existed for more than a decade. I am not very good at googling old stuff, but I remember using curl natively in 2004 or so.
- MandieD 10y ago
  "Native" for Windows means comes out of the box or as an official release from Microsoft, according to many enterprise security teams. PowerShell was not allowed on stuff here until Microsoft started including it with the OS, even though Microsoft fully supported it on downlevel OSes.
Aissen 10y ago
wget has been on windows for 15 years: http://web.archive.org/web/*/http://gnuwin32.sourceforge.net/packages/wget.htm http://web.archive.org/web/*/http://gnuwin32.sourceforge.net... PowerShell first appeared 9 years ago. Edit: curl has been on windows for at least 14 years according to this: https://curl.haxx.se/mail/archive-2002-06/0114.html https://curl.haxx.se/mail/archive-2002-06/0114.html Edit 2: 17 years: http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/www/utilities/curl/ http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/www/util...
- wangchow 10y ago
  They have been on there, but not as standard Windows components. Perhaps they had lofty goals to replace the tools with a "better" version and changed direction.
  - exo762 10y ago
    Replacing something with "better" version is step #2 of EEE.
    - oldmanjay 10y ago
      Replacing something with a better version is also the basis of the success of life. It's all in how you approach things.
    - eitland 10y ago
      If you are going to argue that Microsoft is out on a new EEE trip you are going to have a hard time now that it releases everything as Open Source.
      - dragonwriter 10y ago
        > now that it releases everything as Open Source. Windows? Office? SQL Server? Seems to me, that Microsoft now releases "everything" as open source only by the most ridiculously limited definition of "everything".

warfangle 10y ago

On the other hand, curl.exe has been available for five years.

doikor 10y ago
PowerShell was originally designed so that you would mostly just run CmdLets with it so colliding with an actual program wasn't considered an issue. And these aliases haven been available since 2007. They even admitted it them self that it was stupid and needs to be fixed though so just wait I guess? edit: As a separate note I really would like to have versions of curl and wget that actually have all the params working but return the correct PowerShell objects (so the web request result thingie) instead of a String object. Or maybe have it do that with a flag or something.
- protomyth 10y ago
  I get the feeling there are a lot of commands that are going to need to be customized for actual typed output. It would be an interesting project to do a usr-bin for PowerShell.
laurent123456 10y ago
curl on Windows existed many years before PowerShell.

shmel 10y ago

>>PowerShell was never planned to be run on anything that ran those cmds natively. Really? I thought that windows versions (native versions, not even cygwin) of wget and curl existed for more than a decade. I am not very good at googling old stuff, but I remember using curl natively in 2004 or so.

MandieD 10y ago
"Native" for Windows means comes out of the box or as an official release from Microsoft, according to many enterprise security teams. PowerShell was not allowed on stuff here until Microsoft started including it with the OS, even though Microsoft fully supported it on downlevel OSes.

Aissen 10y ago

wget has been on windows for 15 years: http://web.archive.org/web/*/http://gnuwin32.sourceforge.net/packages/wget.htm http://web.archive.org/web/*/http://gnuwin32.sourceforge.net... PowerShell first appeared 9 years ago. Edit: curl has been on windows for at least 14 years according to this: https://curl.haxx.se/mail/archive-2002-06/0114.html https://curl.haxx.se/mail/archive-2002-06/0114.html Edit 2: 17 years: http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/www/utilities/curl/ http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/www/util...

wangchow 10y ago
They have been on there, but not as standard Windows components. Perhaps they had lofty goals to replace the tools with a "better" version and changed direction.
- exo762 10y ago
  Replacing something with "better" version is step #2 of EEE.
  - oldmanjay 10y ago
    Replacing something with a better version is also the basis of the success of life. It's all in how you approach things.
  - eitland 10y ago
    If you are going to argue that Microsoft is out on a new EEE trip you are going to have a hard time now that it releases everything as Open Source.
    - dragonwriter 10y ago
      > now that it releases everything as Open Source. Windows? Office? SQL Server? Seems to me, that Microsoft now releases "everything" as open source only by the most ridiculously limited definition of "everything".