Jump to content



Photo

Windows 8: cmd or Powershell?


  • Please log in to reply
47 replies to this topic

Poll: cmd vs Powershell

This is a public poll. Other members will be able to see which options you chose

Which would you like to see in Windows 8?

You cannot see the results of the poll until you have voted. Please login and cast your vote to see the results of this poll.
Vote Guests cannot vote

#1 htcz

htcz

    Neowinian Senior

  • Joined: 22-July 11

Posted 30 October 2011 - 11:59

With Powershell now released 4 years ago, I think it has come time to completely replace cmd in Windows 8. AFAIK, it does 99% of the things cmd does and alot more so why not?

So Windows 8: cmd or Powershell?

I pick Powershell default, no cmd at all. If someone trys to call cmd, it automatically starts Powershell (cmd being a new alias for Powershell) and/or (again cmd being a alias for Powershell) it again automatically starts Powershell but, since it has been called thru a cmd alias, it starts out in a "cmd compatibility mode"


#2 1941

1941

    Banned

  • Joined: 17-July 06

Posted 30 October 2011 - 12:26

CMD is there just for the old folks like me that were used to DOS. :/

#3 OP htcz

htcz

    Neowinian Senior

  • Joined: 22-July 11

Posted 30 October 2011 - 13:24

CMD is there just for the old folks like me that were used to DOS. :/

Powershell is the exact same thing. Any normal and logic command that you use in CMD and/or DOS, is avaliable in Powershell. If it isnt, there is problably something better and more powerful that replaces it (but AFAIK, every command is avaliable)

#4 n_K

n_K

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 19-March 06
  • Location: here.
  • OS: FreeDOS
  • Phone: Nokia 3315

Posted 30 October 2011 - 13:27

Powershell looked pretty god-damn awful when I last launched it on a small screen resolution, I'll stick with cmd and if people try to remove it from working, I'll just get cmd.exe and replace the replaced cmd.exe and powershell.exe with the proper cmd.exe

#5 1941

1941

    Banned

  • Joined: 17-July 06

Posted 30 October 2011 - 13:28

Powershell is the exact same thing. Any normal and logic command that you use in CMD and/or DOS, is avaliable in Powershell. If it isnt, there is problably something better and more powerful that replaces it (but AFAIK, every command is avaliable)


I know that and I agree with you, Cmd should be removed, Microsoft only left it in Windows 7 for the old time users that won't advance themselves with the new technology.

#6 -KJ

-KJ

    ٩(●̮̮̃•̃)۶ 

  • Joined: 21-April 08
  • Location: Texas

Posted 30 October 2011 - 13:36

I just assumed Powershell was a just a more powerful shell extension of CMD, and not a successor. If it runs everything CMD did, then what's the purpose of keeping CMD? Just for familiarity for those who continue to make heavy use of cli?

#7 bruNo_

bruNo_

    "Who are you and why should I care?"

  • Joined: 08-May 07
  • Location: São Paulo, Brazil

Posted 30 October 2011 - 13:40

It depends. I won't use Powershell to just check connectivity in my network, cmd is much faster to do it, windows + r -> cmd and voi la. IMO Powershell is designed for System Administration and scripting.

#8 OP htcz

htcz

    Neowinian Senior

  • Joined: 22-July 11

Posted 30 October 2011 - 13:44

I just assumed Powershell was a just a more powerful shell extension of CMD, and not a successor. If it runs everything CMD did, then what's the purpose of keeping CMD? Just for familiarity for those who continue to make heavy use of cli?

Maybe should have posted this:

http://en.wikipedia....dows_PowerShell

http://en.wikipedia..../Command_Prompt

It depends. I won't use Powershell to just check connectivity in my network, cmd is much faster to do it, windows + r -> cmd and voi la. IMO Powershell is designed for System Administration and scripting.

windows + r -> powershell

or you can set a alias for powershell for example p and type

windows + r -> p

And there you go: Its faster than cmd.

Powershell looked pretty god-damn awful when I last launched it on a small screen resolution, I'll stick with cmd and if people try to remove it from working, I'll just get cmd.exe and replace the replaced cmd.exe and powershell.exe with the proper cmd.exe

When was the last time you used it? We are currently at 2.0 and 3.0 is in preview (might be included in the Windows 8 dev release, not sure)

#9 bruNo_

bruNo_

    "Who are you and why should I care?"

  • Joined: 08-May 07
  • Location: São Paulo, Brazil

Posted 30 October 2011 - 14:27


windows + r -> powershell

or you can set a alias for powershell for example p and type

windows + r -> p

And there you go: Its faster than cmd.


Yes I know that, but I won't invoke powershell just to ping an asset. And this is just ridiculous.

#10 n_K

n_K

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 19-March 06
  • Location: here.
  • OS: FreeDOS
  • Phone: Nokia 3315

Posted 30 October 2011 - 14:52

When was the last time you used it? We are currently at 2.0 and 3.0 is in preview (might be included in the Windows 8 dev release, not sure)

The version included with some addon to XP from back in the day.
But I still don't see why you're anal on trying to get rid of cmd?
McDonalds uses thin clients with DOS, do you think instead they should scrap the thin client idea, get new workstations with core i5s, guis, windows 7 and a load of rubbish that isn't needed, just because they could?

CMD is simple, fast, effective and serves a purpose. Powershell is something completely different and serves a different purpose, it's not meant for everyday use by all users.

#11 Leonick

Leonick

    Neowinian Senior

  • Joined: 16-December 07
  • Location: Sweden

Posted 30 October 2011 - 15:15

They'll probably keep CMD around, there are so many companies out there who just won't update software or scripts and still expect their old to work...
That said I sure hope Powershell will come installed with all versions of Windows 8.

CMD is there just for the old folks like me that were used to DOS. :/

All the same commands can be used.
You don't have to use Get-ChildItem, you can use Dir if you like as it's set up as an alias by default, heck if you're used to a unix command line you can use their commands too, in this case ls.

windows + r -> powershell

or you can set a alias for powershell for example p and type

windows + r -> p

And there you go: Its faster than cmd.

Well, the cmd prompt usually load a whole lot quicker than the powershell one.

#12 Angel Blue01

Angel Blue01

    Neowinian/Star Wars freak

  • Joined: 19-October 01
  • Location: Win95ville, USA

Posted 30 October 2011 - 15:26

Powershell really doesn't get the attention it deserves. It really can replace the old command prompt if more developers and users were willing to try it.

But they need to keep cmd for compatibility. Aren't logon scripts still .bat files, many of which won't work without modification in Powershell?

#13 OP htcz

htcz

    Neowinian Senior

  • Joined: 22-July 11

Posted 30 October 2011 - 17:38


Yes I know that, but I won't invoke powershell just to ping an asset. And this is just ridiculous.

Why invoke cmd just to ping an asset?

And the link you posted to........is that really a reason to use cmd over Powershell? :rolleyes: come on....

CMD is simple, fast, effective and serves a purpose. Powershell is something completely different and serves a different purpose, it's not meant for everyday use by all users.

Powershell, as I have stated, includes everything CMD does and more.

CMD isnt also made for "everyday use by all users". You can do everything in Powershell that you can in CMD. I think people are missing that point...

This is the same arguement about people that stay on Windows XP and dont want to upgrade to Windows 7. The even worse part of this is that Powershell is free....



They'll probably keep CMD around, there are so many companies out there who just won't update software or scripts and still expect their old to work...

Thats why I also made a comment that if something calls cmd, Powershell can be ran in a "cmd compatibility mode" which allows it to run exactly the same as regular cmd. Powershell with backwards compatibility which wouldnt break anything :)

That said I sure hope Powershell will come installed with all versions of Windows 8.

It will :) It comes installed with Windows 7 already


All the same commands can be used.
You don't have to use Get-ChildItem, you can use Dir if you like as it's set up as an alias by default, heck if you're used to a unix command line you can use their commands too, in this case ls.

Exactly. Not only do all CMD commands work, but they have actually made aliases for most unix command lines such as bash. What more can you want?



Well, the cmd prompt usually load a whole lot quicker than the powershell one.

DOS/Windows 3.1/Windows 95/Windows 98/Windows ME (yes I said ME)/Windows 2000/Windows XP/Windows Vista/etc were all faster in a loading sense than Windows 7. Point of yours is?

#14 surrealvortex

surrealvortex

    Neowinian

  • Joined: 15-June 07

Posted 30 October 2011 - 17:57


Yes I know that, but I won't invoke powershell just to ping an asset. And this is just ridiculous.


You invoke cmd to ping? I just do Windows+R and then ping from the run prompt.

#15 qdave

qdave

    Neowinian Senior

  • Joined: 02-October 02
  • Location: Vilnius, Lithuania | Toronto,On

Posted 30 October 2011 - 18:06

I dont know how to use powershell so cmd.