5 ms·

The article mentions that. Every change, no matter how trivial, in cmd breaks some behavior that someone is depending on, or at least it feels that way. Even

The article mentions that. Every change, no matter how trivial, in cmd breaks some behavior that someone is depending on, or at least it feels that way. Even fixing bugs tends to break large number of scripts in the wild. I'd like to see a 'bacmd' or something where they could break some history without fear, but clearly MS has decided to focus their resources on a very different way of thinking for their new shell.

maxxxxx 10y ago
Yes, just freeze the old version and create a new CMD. And while they are at it, make notepad useful.
- mtdewcmu 10y ago
  I can understand why notepad is simple. You can easily install alternatives, like notepad++.
  - roywiggins 10y ago
    Does Notepad understand Unix line endings yet?
    - WaxProlix 10y ago
      No.
      - bbcbasic 10y ago
        That's part of its charm, like the two state undo buffer
    - romwell 10y ago
      No, but wordpad does - use it in lieu of Notepad when you need to edit text on a Windows machine and don't want to install external tools.
      - logicchains 10y ago
        Or open in wordpad, save (which will convert the line endings), then open again in notepad and edit there.
mtdewcmu 10y ago
There are possible improvements that wouldn't affect the scripting language. *nix separates out the terminal (e.g. xterm) from the shell (e.g. bash).
- dfox 10y ago
  Windows also separates that, although the separation is slightly different. For example, much of the line editing and tab completion in cmd is actually implemented by the console window itself.
quotemstr 10y ago
Bullshit. cmd has an extension mechanism specifically designed to allow for breaking extensions [1] to the cmd command language. This mechanism hasn't been used very much, but in principle, you could easily add new SETLOCAL [1] commands to enable support for modern command shell features. But cmd is in "maintenance mode", which means nobody is interested in adding features. Powershell is the new hotness. And Powershell wouldn't even be so bad if some of the more shameful problems were fixed --- a pipe between two native programs should be 8-bit clean! [1] https://technet.microsoft.com/en-us/library/bb491001.aspx https://technet.microsoft.com/en-us/library/bb491001.aspx
- ygra 10y ago
  It'd also be of dubious value by now. Cmd has been feature-stable since Windows 2000, I think. Any features added now (i.e. available only in Windows 10, update.next) would not be used by anyone since oftentimes batch files are used where you need stuff to work on pretty much every Windows installation. (Or they are so simple that they wouldn't benefit anyway.)

maxxxxx 10y ago

Yes, just freeze the old version and create a new CMD. And while they are at it, make notepad useful.

mtdewcmu 10y ago
I can understand why notepad is simple. You can easily install alternatives, like notepad++.
- roywiggins 10y ago
  Does Notepad understand Unix line endings yet?
  - WaxProlix 10y ago
    No.
    - bbcbasic 10y ago
      That's part of its charm, like the two state undo buffer
  - romwell 10y ago
    No, but wordpad does - use it in lieu of Notepad when you need to edit text on a Windows machine and don't want to install external tools.
    - logicchains 10y ago
      Or open in wordpad, save (which will convert the line endings), then open again in notepad and edit there.

mtdewcmu 10y ago

There are possible improvements that wouldn't affect the scripting language. *nix separates out the terminal (e.g. xterm) from the shell (e.g. bash).

dfox 10y ago
Windows also separates that, although the separation is slightly different. For example, much of the line editing and tab completion in cmd is actually implemented by the console window itself.

quotemstr 10y ago

Bullshit. cmd has an extension mechanism specifically designed to allow for breaking extensions [1] to the cmd command language. This mechanism hasn't been used very much, but in principle, you could easily add new SETLOCAL [1] commands to enable support for modern command shell features. But cmd is in "maintenance mode", which means nobody is interested in adding features. Powershell is the new hotness. And Powershell wouldn't even be so bad if some of the more shameful problems were fixed --- a pipe between two native programs should be 8-bit clean! [1] https://technet.microsoft.com/en-us/library/bb491001.aspx https://technet.microsoft.com/en-us/library/bb491001.aspx

ygra 10y ago
It'd also be of dubious value by now. Cmd has been feature-stable since Windows 2000, I think. Any features added now (i.e. available only in Windows 10, update.next) would not be used by anyone since oftentimes batch files are used where you need stuff to work on pretty much every Windows installation. (Or they are so simple that they wouldn't benefit anyway.)