3 ms·
It's not changing overnight. It's changing in preview builds to get feedback from power users who asked for immediate changes as they happen. That change might
by WorldMaker 10y ago
It's not changing overnight. It's changing in preview builds to get feedback from power users who asked for immediate changes as they happen. That change might eventually make its way into the Creator's Update several months from now and power users will definitely be forewarned by then.
A learning curve does not make anything "demonstrably inferior" and a lot of the jargon you felt like outright ignoring can lead to rabbit holes where PowerShell really shines, if you let it.
For the most part you've got a transcript equivalent to a DOS user switching to unix and having a hard time figuring out that dir is now ls and ls has a bunch of weird flags and hidden files start with dots for some weird reason... It's not really a demonstration of "inferiority" but a travelogue of ignorance.
You complain about the help system of PowerShell, but when was the last time you even tried HELP.EXE for CMD help? If you want to talk about terrible documentation, there's a field day to be had in HELP.EXE. I remember trying to learn from DOS 5.x's HELP.EXE which was even worse back then.
I'm sorry you don't feel like learning something new, but PowerShell is better than CMD if you give it a chance and maybe not glossing over so much of the jargon?
«What is a cmdlet? Is that like a batch file?»
For the most part yes, a cmdlet is like a batch file but more powerful.
«Where did all this stuff about properties and methods on objects come from? I'm trying to get a directory listing, not write a GUI in Java!»
That's where the magic in PowerShell lies, that's the rabbit hole to follow if you want to start seeing what makes PowerShell special.
- Silhouette 10y agoI'm sorry, but I think we're still talking at cross-purposes here. It is a fact that Microsoft can and do roll out significant changes to Windows 10 literally overnight and without giving many users the option to decline them. It is reasonable to assume from the fact that this discussion was relevant at all that Microsoft are at least considering doing that with this change, but even if they don't, the general point still stands. Whether or not Powershell is more powerful than the command prompt once learned is still not the point. The point is that it is different, and if this change goes ahead, something that worked yesterday in the same way as it had for literally decades will suddenly not work the same way tomorrow. As a final note, you seem to have confused my description of my initial experience with the then-new Powershell something like a decade ago with my current situation, but again, that really isn't the point anyway. The point is that forcing such a change on users could create at best a good deal of confusion and frustration among existing users who already know the current system they've been using for a long time. The comparison isn't between learning Powershell and learning cmd or bash, it's between learning Powershell and not having to do anything at all. The poor documentation and general clumsiness and verbosity of Powershell are merely rubbing salt in the wound at that point.