Live data from Hacker News

Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

news.softpedia.com

11–20 of 350 posts

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

#12

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.

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

#13
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?

It's actually 'powershell' and not just 'ps', but you are right. Typing 'powershell' gets you to PS and typing 'cmd' gets you the command prompt.

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

#15
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)

Both DIR and LS do list directories in PowerShell.

But all parameters on DIR and LS seem to result in errors, even "dir /h", "dir /?", "dir -h", "dir --help", etc. That is a bit annoying.

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

#18
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

But are all cmd commands portable verbatim to powershell? With all the options / special characters? (I don't know the answer, but https://en.wikipedia.org/wiki/PowerShell#Comparison_of_cmdle... lists quite a few missing commands, including "talkkill" and "find")

With the amount of online posts that tell you "to achieve X, open command prompt and run ...", it would be a bad idea to break any of them that go beyond a simple command. (so for example any "FOR ..." lines)

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

#20

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.

If you're not a fan of change, I feel like software development probably isn't the right career choice.
Post reply on HN