Decouple cmd and powershell from main windows updates release cycle
With the move to get most things into the windows store and otherwise automatically updating themselves a-la evergreen web-browsers, and even windows-as-a-service, why not consider a similar evergreen approach for cmd and powershell? Remove the requirement to be tightly bound to the base system thereby allowing more incremental and faster-cadence releases.
Daniel Llewellyn
shared this idea
PowerShell was recently open-sourced: https://github.com/powershell/powershell
Cmd is the original Windows command-line shell interpreter and rarely changes in order to maintain compatibility with the billions of scripts run on hundreds of millions of machines every day.
The Windows console is the terminal/console window used by cmd, PowerShell, Telnet, Ping, Bash on Windows, etc. and is an integral and essential part of Windows: In fact, Windows cannot even boot without the Console’s engine being present and working as expected!
We do agree that it’d be cool if we could deliver a console via the store, but that’s a project for another day ;)
1 comment
-
Oisín Grehan commented
A common misunderstanding, but powershell.exe and cmd.exe have nothing to do with the windows console. Those things are applications; the console is a set of APIs allowing text mode applications (like cmd and powershell) to have a tty (screen) and a means of input (keyboard/mouse.)