3 ms·
I'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
by Silhouette 10y ago
I'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.