Live data from Hacker News

Coreutils for Windows

github.com

101–110 of 260 posts

Re: Coreutils for Windows

#101

I wonder if the motivation is to make Ai agents work better on Windows?

The intent was simply to give people coming from macOS and Linux more of the CLI tools they're familiar with. In other words, agents weren't the focus at all. But if it ends up helping them, that's a good added benefit of course.

Re: Coreutils for Windows

#102
post #70
post #63

Earlier quoted context omitted.

On Windows, I've mostly avoided CRLF by configuring text editors and git to use LF, and writing text files in binary mode. The only places that still forced CRLF were batch files and clipboard.

> I've mostly avoided CRLF by configuring text editors and git to use LF, That has been my experience as well. I can't remember the last time I had an issue related to CRLF.

Yesterday for me was the last time. Visual studio 2026 default to crlf I think maybe and I have autoctlf in git turned off. I should probably turn that back on.

Re: Coreutils for Windows

#104
post #6

So dir is not shipped due to conflict with built-ins, echo and rmdir are shipped despite conflicts, and sort is deemed not to have a conflict? What is the logic?

As hex4def6 said, the idea was that DOS command conflicts are not a good idea, while overriding PowerShell builtins in interactive sessions (PSReadLine) is acceptable, if not a good idea. We open-sourced DOS sort and published a port of the DOS find command. The suite then dispatches to the GNU/DOS variant based on heuristics.

Re: Coreutils for Windows

#105

In the intentionally dropped section, it lists shed as "Not particularly useful on Windows." Does anyone know why? Is thre already a shred-like command in Windows?

Shred isn't very useful on SSDs in general. Because of TRIM, deleting a file instantly makes the sectors read back as 00 bytes. (Yes the data is technically still on the flash chips scattered across memory blocks without any mapping telling you where each piece of the data is, but is not readable through normal drive commands)

Re: Coreutils for Windows

#106
For the MS folk reading this: native zsh on Windows, please?

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.

Re: Coreutils for Windows

#107

I would have liked to see head, tail, tr, uniq, and cut. I end up dragging over the old "gnuwin32" versions of those to a lot of Windows machines. Those are my go-to tools for quick-and-dirty log analysis. 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 Uni…

> I would have liked to see head, tail, tr, uniq, and cut.

The project includes all of those. Or were you talking about the past?

Re: Coreutils for Windows

#108

I feel like I'm seeing an error, or I just don't understand what they mean w/ "find" and "Integrated port of the original DOS command" and not listed as conflicting. 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…

We actually open-sourced DOS sort and published a port of the DOS find command. The suite then dispatches to the GNU/DOS variant based on heuristics. The installer allows you to pick what variant to use by default if the invocation is ambiguous.

Re: Coreutils for Windows

#110

A fair question is why this fork of coreutils is required when the original Rust rewrite ( https://github.com/uutils/coreutils/ ) supports Windows, in addition to Linux, macOS and wasm. 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.

The original one is not virtue signaling enough
Post reply on HN