WSL VS setup-msys2

There have been massive GitHub issue spams recently, including in Microsoft's WSL repository.

https://github.com/microsoft/WSL/issues/40028

Reference: https://github.com/microsoft/WSL/issues/12586

The Windows filesystem isn't slow per se, it's a slowness caused by "a thousand cuts" type of problem.

https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

You might be missing context here.

There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).

https://github.com/microsoft/WSL

The feature is a windows subsystem (for running Linux).

I mean inside WSL. E.g. running nested virtual inside WSL env. https://github.com/microsoft/WSL/issues/11216#issuecomment-2... for details.

I use a WSL backend and there seems to be some issues with file watching (You can read more about it here and here). This means that automatic recompilation on save does not work, this is why I add the --manual-run flag in the initialization. On other systems this might work without issues.

👉 Baixar WSL 2.3.24 (MSI)

/? mingw: https://github.com/search?q=mingw&type=repositories

msys2/MINGW-packages: https://github.com/msys2/MINGW-packages ; [..., SDL, gles, glfw, egl, glbinding, cargo-c, gstreamer, gtest, cppunit, gtk4, icu, jack2, gnome-text-editor, gtksourceview, kdiff3, libgit2, libusb, libressl, libsodium, libserialport, libslirp, hugo]

msys2/setup-msys2: https://github.com/msys2/setup-msys2:

> setup-msys2 is a GitHub Action (GHA) to setup an MSYS2 environment (i.e. MSYS, MINGW32, MINGW64, UCRT64, CLANG32, CLANG64 and/or CLANGARM64 shells)

Though, if you're writing a 3d app/game, e.g. panda3d already builds for Windows, Mac, and Linux.

panda3d > Building applications: https://docs.panda3d.org/1.11/python/distribution/building-b... :

mstorsjo/llvm-mingw:

Other pages provide complementary information on that same topic.

Another thing I appreciated was the explanation of MSYS2's environments:

https://www.msys2.org/docs/environments/

Being able to painlessly switch away from MSVCRT to UCRT was helpful in solving some UTF-8 difficulties I was experiencing at the time.

Package management with pacman is rather pleasant, and the setup-msys2 GitHub Action makes it simple to provide your GHA workflow with the tools and libs you want:

https://www.msys2.org/docs/package-management/

https://packages.msys2.org/queue

https://github.com/msys2/setup-msys2

> Actions reduce workflow steps by providing reusabe[sic] “code” for common tasks. To run an action, you include the uses keyword pointing to a GitHub repo with the pattern {owner}/{repo}@{ref} or {owner}/{repo}/{path}@{ref} if it’s in a subdirectory. A ref can be a branch, tag, or SHA.

Aside from the typo, I wonder how many packages could be backdoored at once, if an action maintainer went rogue, seeing as there's no pinning for actions by default, and (according to https://github.com/msys2/setup-msys2/blob/main/HACKING.md) moving a tag is the default way to push updates to an action. (Interestingly get-cmake/run-cmake/run-vcpkg are all operated by the same person.)