- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
I always thought PowerShell was just the blue cmd
I often develop on Windows, but I have never really understood the difference between Command Prompt and PowerShell. I always thought PowerShell was just the blue version of cmd.
- Command Prompt, a batch scripting language, is traditionally used to execute DOS commands and batch scripts. Its syntax is simple, suitable for handling basic file operations and system administration tasks, and it still exists to support legacy habits and programs.
- PowerShell, a scripting language based on .NET, adapts to user habits, automatically mapping DOS commands to their corresponding command sets. For example, the command
cd
actually executesSet-Location
behind the scenes. In summary: PowerShell is the modern cmd, with more powerful and comprehensive features.
So next time I encounter the two, I won’t think of PowerShell as just the blue Command Prompt anymore (although most of the time, there really isn’t much difference). I suddenly realized that the programming language that initially inspired me to code wasn’t Visual Basic or JavaScript, but Batch Script!
Windows Powershell vs Command Prompt: What’s The Difference Anyway? - ThioJoe
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1