Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#1

Post by ctoth » Fri, Nov 18, 2016, 11:42 AM UTC

Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
news.softpedia.com

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#2

Post by 6u54wuwu5w » Fri, Nov 18, 2016, 12:28 PM UTC

So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#3

Post by FLGMwt » Fri, Nov 18, 2016, 12:48 PM UTC

"Typing cmd in the run dialog will launch PowerShell as well"

What? I'm a big PowerShell fan, but I see the need to keep cmd around for a while. Clobbering it before it's phased out seems problematic.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#4

Post by hugja » Fri, Nov 18, 2016, 1:08 PM UTC

I'm probably wrong, but can you not type "ps" into CMD and get the PowerShell prompt? If so, can you do it the other way around as well?

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#5

Post by godzillabrennus » Fri, Nov 18, 2016, 1:10 PM UTC

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.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#6

Post by freedrock87 » Fri, Nov 18, 2016, 1:12 PM UTC

FLGMwt wrote: post #3

"Typing cmd in the run dialog will launch PowerShell as well" What? I'm a big PowerShell fan, but I see the need to keep cmd around for a while. Clobbering it before it's phased out seems problematic.

You can run any command from CMD in Powershell

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#7

Post by louhike » Fri, Nov 18, 2016, 1:16 PM UTC

6u54wuwu5w wrote: post #2

So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?

It's better but it's still slower than CMD on my computers.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#8

Post by algorithmsRcool » Fri, Nov 18, 2016, 1:16 PM UTC

hugja wrote: post #4

I'm probably wrong, but can you not type "ps" into CMD and get the PowerShell prompt? If so, can you do it the other way around as well?

you can run "powershell" from a CMD prompt and "cmd" from a powershell prompt.

You can also nest prompts to switch context between them.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#9

Post by richard_todd » Fri, Nov 18, 2016, 1:17 PM UTC

6u54wuwu5w wrote: post #2

So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?

Funny, that was my first thought as well. Sometimes I start cmd.exe instead of powershell on rotating-disk machines because of the startup time. On SSDs I find the startup time is negligible.

Re: Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

#10

Post by algorithmsRcool » Fri, Nov 18, 2016, 1:19 PM UTC

louhike wrote: post #7

6u54wuwu5w wrote: post #2

So, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?

It's better but it's still slower than CMD on my computers.

In particular if you have left the prompt window untouched for a few hours and it has been paged out. Just pressing to complete a file name will hang for 3-6 seconds on my computer while PS wakes back up.

CMD is always instantaneous.

I realize that PS is doing a lot more work to match commands but sometimes simple is all that is needed.