Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by bitwize on Friday November 18, 2016 @12:05PM (#12988185)

> PowerShell's terminal experience is better but not quite there. And, PS suffers from extremely long load times - I've seen it take upwards of 10 seconds to start without any extensions.

Small price to pay to be able to pipe objects, man!

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by JeffreySnover on Friday November 18, 2016 @09:03PM (#12991586)

Sorry about that - we lost control of our startup times in PS V3 and have been working to get it back under control. PowerShell V5 had substantial improvements but we keep working on it and V5.1 is even faster. Give it a try - I think you'll like it.

Jeffrey Snover [MSFT]

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by Bombthecat on Saturday November 19, 2016 @03:16AM (#12992565)

I really hope so!

I basically stopped using ps ( for smaller stuff) because the startup tone is so awful.

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by nneonneo on Saturday November 19, 2016 @01:42AM (#12992375)

I'm not entirely sure if you're joking or not (one of the hazards of the textual communication medium). Yes, piping objects is fun and occasionally very useful, but waiting ten seconds to pop a terminal so I can run `ipconfig` or something is not so useful.

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by throwaway7645 on Friday November 18, 2016 @07:19PM (#12991126)

Are you actually able to not be confused by piping objects? In Unix everything is a string so I just pipe text to sort and then unique...etc. PS always complains relentlessly. The GUI features and .NET integration is nice though.

[ Parent | on HN ]