Hi all,
I'm super excited about SwiftNIO for Windows support but I after asking around and sifting through the GitHub issues, I was not sure what the status or outstanding work was needed to get SwiftNIO for Windows support. When searching GitHub, I only see this issue from 3 years ago.
I am happy to sponsor work to move it through!
Any guidance on a plan or architecture? Perhaps @lukasa @gregcotten I see you two as some of the latest commenters?
Max
I'd like to add my voice to the desire to have SwiftNIO on Windows.
Swift on Windows has seen fantastic progress, and to ensure Swift's long-term success as a supported language on multiple OSes, including Windows, package developers must be shown the path to supporting Windows as early as possible in their roadmap. Otherwise, we end up with orphans or multiple forks per platform, with all the inconveniences that entail.
I would love to have Vapor on Windows (which depends on NIO), even if the performance isn't optimal. There's nothing new in this respect; as programmers, it's our job to make future releases of a project aimed at performance optimizations, but at least initially, to ensure the product is available.
We are expecting to kick work off in this space imminently.
Is there anything I or my team can do to help?
If you'd like to start working on getting things to compile, that would work great. Certainly up to the NIOPosix layer that shouldn't be excessively hard.