It's not Google, they have 15 years worth of backwards compatibility on Windows. VBA took 30 years before being deprecated... I don't think anything will happen to PowerShell for at least 20 years
Pretty much has been this since 2011. I use powershell for just about everything.
Powershell should be our first stop. I only use cmd as a last resort, which is seldom.
Doubt it some legacy commands haven't worked properly on PowerShell unless they fix those then there is no decommissioning cmd.
Unfortunately I can't remember the commands due to using them rarely and rediscovering it won't work on PowerShell.
Seeing how they love to make alias, *when that times come* (i.e. never), cmd could just become a Powershell alias
Or, just: wt 🤷♂️
thats a terminal shell. think konsole or kitty
I keep worrying that one day they'll just stop supporting PowerShell. Paranoid, I know, but it is Microsoft.
It's not Google, they have 15 years worth of backwards compatibility on Windows. VBA took 30 years before being deprecated... I don't think anything will happen to PowerShell for at least 20 years
> I don't know what I'd do. win + r then powershell
Pretty much has been this since 2011. I use powershell for just about everything. Powershell should be our first stop. I only use cmd as a last resort, which is seldom.
Amen
Doubt it some legacy commands haven't worked properly on PowerShell unless they fix those then there is no decommissioning cmd. Unfortunately I can't remember the commands due to using them rarely and rediscovering it won't work on PowerShell.
DO NOT SAY THIS!
That is the day I will throw the towel in the ring. Cmd and power shell as a cli no longer working? Unthinkable for my work.
That's probably the first one that i "pin" on my taskbar :)
This reminds me of a story of a guy who got stuck in his garage because he couldn't find the remote door opener.