Is CMD subset of Windows PowerShell?

  • Thread starter Thread starter yungman
  • Start date Start date
  • Tags Tags
    Computing
Click For Summary

Discussion Overview

The discussion revolves around the comparison between CMD (Command Prompt) and PowerShell, focusing on whether CMD is a subset of PowerShell and which one should be learned first. Participants share their experiences and opinions on the relevance and utility of both tools in the context of learning basic computer skills.

Discussion Character

  • Exploratory
  • Debate/contested
  • Conceptual clarification

Main Points Raised

  • Some participants suggest that CMD is fundamental for using Windows and scripting, while PowerShell is seen as more advanced.
  • Others express uncertainty about the necessity of learning both, with some preferring to start with CMD due to its perceived simplicity.
  • A participant mentions that many CMD commands also work in PowerShell, with exceptions noted.
  • There is a suggestion that CMD is older and less sophisticated than PowerShell, dating back to the DOS era.
  • Some participants share links to resources for further information on the differences between CMD and PowerShell.

Areas of Agreement / Disagreement

Participants do not reach a consensus on whether CMD is a subset of PowerShell or which tool is more beneficial to learn first. Multiple competing views remain regarding the relevance and complexity of each tool.

Contextual Notes

Participants express varying levels of familiarity with both CMD and PowerShell, and there are references to specific commands and their functionalities, which may depend on individual use cases and definitions.

yungman
Messages
5,741
Reaction score
291
Hi

I never learn CMD all these years. I am getting a little more into computer, PowerShell is completely new to me. I just want to get opinions from you experts whether I should learn PowerShell or just learn CMD.

I read articles that CMD literally a subset of PowerShell.

I am not that into IT or anything, just want to learn a little. Should I just learn CMD alone?

Thanks
 
Last edited:
Computer science news on Phys.org
berkeman said:
I've mostly use CMD in my work, but also looked briefly at Powershell a couple years ago for some specialized tasks. Others can give you good answers, but I did a Google search on CMD vs Powershell and got lots of good hits:

https://www.google.com/search?client=firefox-b-1-e&q=cmd+vs+powershell&bshm=rimc/1
So CMD is more popular? I don't want to learn more than I need. I just want some idea. I learn computer after DOS, never get into it before. Just want to learn some.

Thanks
 
yungman said:
So CMD is more popular? I don't want to learn more than I need.
You should know by now that you should not trust my word on this stuff... :wink:

CMD commands are pretty fundamental to using Windows/DOS boxes and scripting. When I looked at Powershell I was trying to figure out how to use the linux "expect" command reliably on Windows. It's a more advanced command that you would only look at using in specialized circumstances, IMO.
 
  • Like
Likes   Reactions: Tom.G and yungman
berkeman said:
You should know by now that you should not trust my word on this stuff... :wink:

CMD commands are pretty fundamental to using Windows/DOS boxes and scripting. When I looked at Powershell I was trying to figure out how to use the linux "expect" command reliably on Windows. It's a more advanced command that you would only look at using in specialized circumstances, IMO.
I've been away from Windows for a long time (I'm happy to say. POSIX offers so much more control but of course Windows is still an industry standard and won't be going away anytime soon.)

There's a lot of easily accessible information about the differences between PowerShell and CMD:

Just off the top of google:

How PowerShell Differs From the Windows Command Prompt

What's new in PowerShell Docs for 2023PS.:

Is "debug" also a command in PowerShell? :)
 
berkeman said:
You should know by now that you should not trust my word on this stuff... :wink:

CMD commands are pretty fundamental to using Windows/DOS boxes and scripting. When I looked at Powershell I was trying to figure out how to use the linux "expect" command reliably on Windows. It's a more advanced command that you would only look at using in specialized circumstances, IMO.
I think I am going to learn CMD first. I already starting to learn how to change directory like file explorer using "cd" and "cd..". Using TAB to do shortcut.

Thanks
 
  • Like
Likes   Reactions: berkeman
berkeman said:
You should know by now that you should not trust my word on this stuff... :wink:

CMD commands are pretty fundamental to using Windows/DOS boxes and scripting. When I looked at Powershell I was trying to figure out how to use the linux "expect" command reliably on Windows. It's a more advanced command that you would only look at using in specialized circumstances, IMO.
I learned some of the commands in CMD like cd, TAB to scroll through directory alphabetically, dir, cls, dir * etc. They ALL work in Powershell. So far the only one that doesn't work is "/a" to view hidden files.

I am not done yet, I only gone through 1/2 of the 9 part series on CMD commands.
 
Try the /? option to dir. dir /?

Many (all?) commands, and even programs, accept the /? to show a list and descriptions of their known options.

Cheers,
Tom
 
yungman said:
So CMD is more popular?
It's older and a lot less sophisticated than PowerShell. The CMD commands date from the time before Windows was released when IBM PC clones ran some form of DOS, like PC-DOS or MSDOS.
 
  • Informative
Likes   Reactions: berkeman

Similar threads

  • · Replies 12 ·
Replies
12
Views
4K
  • · Replies 16 ·
Replies
16
Views
5K
  • · Replies 7 ·
Replies
7
Views
1K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 6 ·
Replies
6
Views
3K
  • · Replies 6 ·
Replies
6
Views
2K
  • · Replies 4 ·
Replies
4
Views
3K
  • · Replies 23 ·
Replies
23
Views
3K
  • · Replies 13 ·
Replies
13
Views
1K
Replies
17
Views
6K