Linked by Thom Holwerda on Fri 18th Nov 2016 15:56 UTC

Command Prompt has been around for as long as we can remember, but starting with Windows 10 build 14971, Microsoft is trying to make PowerShell the main command shell in the operating system.

As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app. Additionally, in File Explorer’s File menu and in the context menu that appears when pressing Shift + right-click in any folder, the old Command Prompt will no longer be available.

Typing cmd in the run dialog will launch PowerShell as well, so Microsoft has made a significant step towards phasing out the traditional Command Prompt.

It's funny - cmd has always been seen as a sort-of Baby's First Command Line, and compared to the shell that comes standard with any UNIX-based operating system, that was certainly true. However, now that Windows has a replacement that is much more capable than cmd, people will cry foul and hell over the possible deprecation of cmd.

Us nerds are fickle.

Permalink for comment 637395
To read all comments associated with this story, please click here.
Member since:

I've done some scripting in python, which is both user-friendly AND powerful at the same time. There's no reason a shell can't be as well. I guess holier-than-thou pricks like you don't want it to be, but whatever. It still doesn't negate my original point that bash definitely isn't.

I've done my fair share (more than?) of Python, Bash, Batch, and other kinds of programming.

Shell Scripting (Bash, Batch) is something a little different than all the rest (Python, JavaScript, etc); you don't get the ability to write several lines and link them together to do stuff, and keeping shells working generally the same helps people be able to switch between them - which they need to do a lot more readily than they do programming languages.

So....having the common use of 2&>1 to redirect helps people in many ways. Variables in shell scripting don't quite work like they do in full language environments (e.g Python interpreter).

All that to say - you have to stop expecting features of full dev environments (e.g Python Interpreter, JVM, etc) to that of lower forms (e.g shell scripting). They are targeting different use cases, different needs, etc.

Reply Parent Score: 2