Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Post by kabdib » Fri, Nov 18, 2016, 1:39 PM UTC

dfcowell wrote: post #17

godzillabrennus wrote: post #5

Just another reason to stay away from Windows as a platform. Windows 10 is a moving target if you are trying to work with it.

PowerShell is fully backwards compatible with cmd. Try again.

Post by shostack » Fri, Nov 18, 2016, 1:40 PM UTC

poizan42 wrote: post #12

godzillabrennus wrote: post #5

Just another reason to stay away from Windows as a platform. Windows 10 is a moving target if you are trying to work with it.

How is that any different from Linux distributions camping their default shell? Like back when debian changed their default shell to dash I don't remember anyone saying you should stay away from debian, even though it broke a lot of existing scripts.

Post by pawadu » Fri, Nov 18, 2016, 1:40 PM UTC

taspeotis wrote: post #14

pawadu wrote: post #11

So basically instead of doing dir C:\ I have to learn to type List-Directory-With-Files Drive=C Folder=/ (made up example, but you get the point)

http://imgur.com/kDQVBZw

Post by taspeotis » Fri, Nov 18, 2016, 1:43 PM UTC

pawadu wrote: post #26

taspeotis wrote: post #14

Earlier quoted context omitted.

http://imgur.com/kDQVBZw

Sure, go ahead, ruin my joke :) More seriously, how many seconds did it took for the PS to answer to that command?

    Measure-Command {dir C:\}
    TotalMilliseconds : 2.9708

    Measure-Command {Get-ChildItem "C:\"}
    TotalMilliseconds : 2.4161

Post by douche » Fri, Nov 18, 2016, 1:44 PM UTC

pawadu wrote: post #11

So basically instead of doing dir C:\ I have to learn to type List-Directory-With-Files Drive=C Folder=/ (made up example, but you get the point)