In powershell everything is much better than cmd, but it's just not enough.

WSL is generally great, but there are annoying downsides. I often get "catastrophic" crashes and the zone identifier files drive me nuts. Plus it takes so much longer to start VSCode when connecting with WSL, and now you've got two file systems. WSL1 was in many ways better than WSL2 for these reasons.

Well this is not very satisfying, what about proving a way where it actually works without us having to guess where the failure root cause happens to be?

The reason seems to be a few windows specific fixes (https://github.com/uutils/coreutils/compare/main...microsoft...) which can probably be upstreamed into the main repo.

I know I could use Powershell for those kinds of tasks, and I certainly do make a lot of use of Powershell, but the familiarity of those simple tools and the decades-old "muscle memory" of using them on various Unix, Linux, and Windows boxes makes them hard to ditch.

More project information: https://gitforwindows.org/

Official download: https://git-scm.com/install/windows

I didn’t see less or a decent pager. MS needs their analytics on WSL and implement the top 50 commands on powershell

Powershell is very good, but lacks brevity and convenience of coreutils so this should be a big win.

winget install -e --id frippery.busybox-w32

There's a "%SystemRoot%\System32\find.exe" on every Windows NT-derived OS. That's absolutely a conflict.

Also, the "find" command from "findutils" is in no way functionally similar to the "original DOS command" (which is for finding text in files).

Aside: Eschew "find.exe" on Windows for "findstr.exe". The latter is vastly more efficient. I discovered that by happenstance once and have trained my hands to type "findstr" when I mean "find" on Windows.

WSL2 is great, but native POSIX is even better. Of course it’s a big undertaking, but it makes Windows a first-class dev platform for those who need POSIX in production.

On Windows it is possible of course, WSL, msys, what not, but it is cumbersome. And I hate the default compiler on windows. So if coreutils on windows helps simplify all the base toolchain, I am all in favour of it. Windows really needs to make compiling stuff a LOT easier by default. I don't want to download some x GB of stuff I don't really need.

Wine and other compatibility layers show that non-trivial software doesn't work if even one of the many layers uses something unsupported.

https://github.com/rmyorston/busybox-w32

https://www.gnu.org/software/coreutils/manual/html_node/ln-i...

https://uutils.github.io/coreutils/docs/utils/ln.html

If anyone from MS is reading this can we please also get an equivalents (or even alias) for the thing that shows IP address? The windows equivalent of "ip a" is some convoluted PS command that I can never remember

Remove batch, VBS and switch from powershell 5 to 7, add bash

Replace DSC in favour of Ansible

Remove windows registries

Switch to systemd for services

Rename folders like Users to home, programdata to etc, program files to opt, store/winget apps /usr

and call it microsoft linux server hybrid

It’s annoying enough to support the differences between BSD and Linux, and now Linux has GNU and uutils, and now we’re gonna need Windows variant of uutils…ugh.