On Sun, Sep 29, 2024 at 10:12 AM Radek Barton <radek.bar...@microsoft.com> wrote: > > Hello Mark. > > I am working on Cygwin/MSYS2 Arm64 port though this is something that could > not be > delivered in matter of months. Can you please describe your use/business case > more > in detail to help up understand the priorities? Why is MSYS2 32bit or, e.g. > WSL, not > working for you?
WSL has a couple of problems for us: - WSL is far too big (many GB), Cygwin's core parts (cygwin1.dll) is small (10MB, full useable cygwin can be reduced to 40MB) - WSL cannot be deployed as part of a product, i.e. Cygwin can be bundled with a product or project, WSL is completely independent - WSL consumes lots of main memory even if not in use, Cygwin is just another Windows DLL - WSL requires separate admin skills, so it is much more expensive for an IT department - WSL is actually a VM with an OS, so it generates CVE which needs to be handled - WSL apps cannot communicate with Windows apps - WSL is buggy. The 9p filesystem network provider keeps crashing for us if you try to access SMB or NFS shares - WSL is not stable for end-user systems. It needs to be bootet, you need to wait until its finished booting, and if you don't shut it down it will corrupt its own filesystem. Permanent headaches with this damn thing Compare this to Cygwin, which is just another Windows DLL, fast and easy to deploy and use, and the Windows admins are not permanently angry about it Mark -- IT Infrastructure Consultant Windows, Linux -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
