The way microsoft just shipped openssh is one of the saner things they have done. I am still vaguely shocked they managed to resist the temptation to MSify it.
Fun fact: They also ship curl.exe, which is different from curl in PowerShell, as the latter is an alias to Invoke-WebRequest. That's one of the insanest decisions they could make during one of the sanest ones.
It is bad because some commands that are in coreutils are conflicting with cmd commands or Windows binaries?
The only thing bad is that take. It's an optional package. It doesn't overwrite any cmd commands or Windows binaries be default. So the user can decide what to install and what to use. It gives full flexibility.
If you say that's a bad choice, I think you're more commenting on your inability to work with these tools, than the tools itself.
It has conflicts all over the place, and requires being skilled across UNIX, Powershell and cmd, to fine tune the PATH and Windows Terminal sessions in order to get the right executables, depending on what one is doing.
As for my skills, I have been coding since 1986, and even though Windows is my main platform, I have used more UNIX flavours in all those years than most HN commmenters.
The way microsoft just shipped openssh is one of the saner things they have done. I am still vaguely shocked they managed to resist the temptation to MSify it.
Fun fact: They also ship curl.exe, which is different from curl in PowerShell, as the latter is an alias to Invoke-WebRequest. That's one of the insanest decisions they could make during one of the sanest ones.
Unfortunately the recent decision to adopt coreutils is similarly bad.
Lots of conflicting commands between UNIX, Powershell and classical cmd.
Thankfully it is still optional, not something shipping in the box.
It is bad because some commands that are in coreutils are conflicting with cmd commands or Windows binaries?
The only thing bad is that take. It's an optional package. It doesn't overwrite any cmd commands or Windows binaries be default. So the user can decide what to install and what to use. It gives full flexibility.
If you say that's a bad choice, I think you're more commenting on your inability to work with these tools, than the tools itself.
It has conflicts all over the place, and requires being skilled across UNIX, Powershell and cmd, to fine tune the PATH and Windows Terminal sessions in order to get the right executables, depending on what one is doing.
As for my skills, I have been coding since 1986, and even though Windows is my main platform, I have used more UNIX flavours in all those years than most HN commmenters.
The most mobile friendly site ever,… said no one.