[Documentation] Please consider providing a rationale as to why coreutils for windows exists.

Open
#7 3 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
cli, documentation

Research direction

The issue does not identify a target file or documentation entry point. Review the project's existing documentation and decide where a rationale and Windows use cases belong; the work is done when readers can understand why Coreutils for Windows exists and when it may be preferable to WSL or MSYS2.

Written by the indexing model from the issue text.

Description

E-needs-discussion

Hey guys,

I found this via hackernews.

Now, on a first read this is cool but ... on a second read I have to ask ... why?

That is, why is coreutils added to windows? Why not just have WSL?

If possible, could you guys considering providing one or more rationales
as to why the project is added? Use cases and so? This may give people
an idea whether they may need it. In particular when they may have
installed msys2 or something like that already.

What can we do thanks to coreutils on windows?

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.