●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Catch up on stories from the past week (and beyond) at the Slashdot story archive
Forgot your password?
Close
Post
Load All Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
| Reply
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
byDrXym ( 126579 ) writes:
PowerShell is longwinded with a bizarro Verb-Noun fixation and a heavy runtime behind it. Yes there are aliases but unfortunately those aliases suck - e.g. when you type "dir" in PowerShell it is an alias on Get-ChildItem which conspicuously not "dir" in the conventional sense and does not support the same arguments.
Would it have killed Microsoft to have written a cmdlet called Get-DosChildItem that behaved like the old command and alias to that? Same for the other commands - deltree, rmdir, cd, cmd, xcopy move, if, rename etc. - and even cmd itself. If they had done that then chances are command prompt would have gone away entirely because PowerShell would be a complete superset. They could have even written decent analogues for Unix file utils in the same way but they didn't do that either.
The only time I'll use PowerShell is when I'm forced to, when there is no other way to do something from a prompt to manage Windows. Otherwise I use a prompt which is terse and familiar and doesn't inflict verbosity or runtime complexity on me for no reason.
Reply to This
twitter
facebook
Flag as Inappropriate
bykwelch007 ( 197081 ) writes:
PowerShell is longwinded with a bizarro Verb-Noun fixation and a heavy runtime behind it. Yes there are aliases but unfortunately those aliases suck - e.g. when you type "dir" in PowerShell it is an alias on Get-ChildItem which conspicuously not "dir" in the conventional sense and does not support the same arguments.
Would it have killed Microsoft to have written a cmdlet called Get-DosChildItem that behaved like the old command and alias to that? Same for the other commands - deltree, rmdir, cd, cmd, xcopy move, if, rename etc. - and even cmd itself. If they had done that then chances are command prompt would have gone away entirely because PowerShell would be a complete superset. They could have even written decent analogues for Unix file utils in the same way but they didn't do that either.
The only time I'll use PowerShell is when I'm forced to, when there is no other way to do something from a prompt to manage Windows. Otherwise I use a prompt which is terse and familiar and doesn't inflict verbosity or runtime complexity on me for no reason.
If that's what you want, it would not be hard to implement yourself. I concede, PowerShell syntax is a bit weird. I'm an old PERL/BASH guy, and PowerShell reminds me a bit of both, so I don't mind much. But getting a good one-liner PS command can get a little hairy.
● threshold.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...