Support WASIX in Zig

[syrusakbary]

Sadly, I've been personally banned from the Zig community for disagreeing with their take stating that Bounties damages open source in a very cordial private conversation with one of their leadership members.

Because of that, and because we still want to offer a $5,000 bounty on Zig supporting WASIX, I'm moving the thread to the Wasmer community directly.

For historic proposes, we have kept an archive of the original issue from Zig before Zig leadership decided to remove most of the comments: https://docs.wasmer.io/wasix-in-ziglang-archive.mht (open the file with Google Chrome once downloaded)

---

The $5,000 bounty would be considered achieved when:

• All C examples from wasix-libc can be compiled correctly from Zig directly into Wasm/WASIX and run properly with Wasmer: https://github.com/wasix-org/wasix-libc/tree/main/examples
• Zig files can be compiled correctly to Wasm/WASIX, with custom examples working
  • Sockets
  • Process spawning
  • Piping

Note: no work will be needed on the Wasmer runtime side (or, if needed, it will be handled by the Wasmer team), since wasix-libc and cargo-wasix already work properly in the runtime. Work will be mainly needed in a Zig fork

Info: while ideally the PR should be merged into Zig master, is not a necessary requirement to receive the bounty. As long as a fork exists that fulfills the requirements laid out before, the bounty will be awarded

[syrusakbary]

Important note, while the $5,000 bounty will be still up, to address some of the comments mentioned by the Zig team on their blogpost, here's what we are going to do:

• Wasmer will manage the work and have at most one person or team working on it at a time. Anyone interested on the work should reply here and organization of the work will be done by the Wasmer team
• Partial work that actually works will be rewarded accordingly (for example, the libc layer, or the Zig layer itself)

Keep up the good work!

[ghost]

Sadly, I've been personally banned from the Zig community for disagreeing with their take stating that Bounties damages open source in a very cordial private conversation with one of their leadership members.

not surprising. @andrewrk is ban happy, and always has been. he uses blocks like most people use the thumbs down emoji, probably more so. any public or private disagreement with him will get you a block.

also to anyone reading this. DONT POST any code to Zig issue tracker. post it to your own repo, and link to it if need be. any code you post to the tracker becomes MIT license, which I learned the hard way. Andrew essentially stole some code I wrote this way, because I didn't know the license implications.

[syrusakbary]

Hey @1268 I don't want to have any subjective judgments on actors involved in the Zig decision of banning sponsorships and my own persona from the Zig community (even though I consider that action quite unfortunate and non-productive). We can do better. The fact that they don't comply with their own CoC (re: "Being respectful of differing viewpoints") doesn't make us free to do the same.

Basically, the comments we should have on this issue should be centered on trying to move WASIX in Zig forward, hope you can understand.

Let's keep this issue as technical as possible to help organize the work on WASIX for Zig 💪

[waynr]

I went into more detail on your HN post, but $5k likely isn't going to tempt people with the skills necessary to take a shot at this. I also agree with the Zig maintainers that it's better for everyone involved if you consider an actual contract with clear terms. I can put you in touch with some recruiters who specialize in finding developers willing to do this kind of work. Good luck!