Coreutils for Windows

1. coreutils

   1 4 21 - Rust

   Coreutils for Windows: Installer & Packaging (by microsoft)

   

   I read the readme that way too - a table with included utils with conflict status, and a list of intenationally excluded utils.

   But the rest are in there:

   https://github.com/microsoft/coreutils/blob/3fa7aaf832ffc81d...

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. busybox-w32

   2 21 868 9.2 C

   WIN32 native port of BusyBox.

   

   There's also a windows port of busybox if you want something more stable. w64devkit uses it.

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

4. coreutils

   3 154 23,761 10.0 Rust

   Cross-platform Rust rewrite of the GNU coreutils

   

   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.

5. git

   4 630 9,290 0.0 C

   A fork of Git containing Windows-specific patches. (by git-for-windows)

   

6. gsh

   5 2 119 0.0 C

   A POSIX shell for Windows. (by AdaCore)

   

   Bash itself is an odd duck in scripting, with some dark historical crevices: http://tiswww.case.edu/~chet/bash/POSIX

   A better option is a pure POSIX shell, the best-known of which in Linux is dash, but there is an existing Ada port to Windows here:

   https://github.com/AdaCore/gsh

   If non-POSIX features are required, the Android decision for mksh might suggest oksh for Windows.

7. STL

   6 167 11,097 9.5 C++

   MSVC's implementation of the C++ Standard Library.

   

   The question is not odd at all. Windows 10 Enterprise LTSC 2019 is supported until 2029: https://learn.microsoft.com/en-us/lifecycle/products/windows...

   Also, MS does absolutely support EoL versions of their OS - it took MSVC's STL until 2024 to finally drop support for Windows 7 (whose final ESU update was 2023): https://github.com/microsoft/STL/issues/4858 - it isn't unlikely that they (STL maintainers) are not going to get approval for dropping Windows 10 support before 2029.

8. msys2-runtime

   7 3 235 8.8 C

   Our friendly fork of Cygwin 💖 https://cygwin.org 💖 see the wiki for details

   

   You're conflating MSYS2 with Mingw-w64. MSYS2 installation comes with multiple environments/ABIs and MSYS2 mode a fork of Cygwin. They fork Cygwin, put some patches on and rename the DLL as msys-2.0.dll . Here is the sources for MSYS2 runtime that produces it: https://github.com/msys2/msys2-runtime . To run bash you need stty, fork, exec. Cygwin implements this via a executable backdoor hack. Since MSYS2 is a fork it uses the same implementation.

   Unlike Cygwin MSYS2's goal isn't to be a complete system but ship just enough tooling to enable development with Mingw-w64. Mingw-w64 is the toolchain that ships GCC and it also defines its own ABI where the C ABI is the same as MSVC / Win32 ABI except that Mingw-ABI comes with its own threading and structured exception handling infrastructure. For C++ Mingw-w32 uses Itanium ABI instead of MSVC. If you use GCC to compile the debugging symbols will be DWARF with Mingw-32.

   You can also use Clang environments where you can generate PDB debug symbols and use native Win32 threading.

Suggest a related project