WinObjC VS cloudabi

Ok, I'm very much paraphrasing from "shit I read on Wikipedia", but WinObjC does exist and it did use parts of GNUStep: https://github.com/Microsoft/WinObjC/issues/116

I was working on emulating apps directly [1] by translating API calls from iOS to Windows APIs using WinObjC [2]. Unfortunately, WinObjC got abandoned and didn't even contain as many APIs as I thought, so the result cannot emulate complex apps. But it was fun.

[1] https://github.com/ipasimulator/ipasim

[2] https://github.com/Microsoft/WinObjC

sometime u just need to use that search input field. https://github.com/microsoft/WinObjC

It's funny when you look at the contribution graph and see that most of the activity happened in the typical tenure length at tech companies (1-2 years)

https://github.com/microsoft/WinObjC/graphs/contributors

There's also https://github.com/Microsoft/WinObjC/ that I've heard of but never looked into

There used to be an alternative runtime for FreeBSD called CloudABI [1], with which native programs could be started in capability mode, but it was discontinued in favour of WASI [2] (server-side Webassembly) — which adopted CloudABI's libc API.

0: <https://www.cl.cam.ac.uk/research/security/capsicum/>

1: <https://github.com/NuxiNL/cloudabi>

2: <https://github.com/WebAssembly/WASI>

Agreed re: the general idea, but isn't CloudABI in particular superseded somewhat by WASI? Its repo seems to say it is: https://github.com/NuxiNL/cloudabi

(WASI is similarly capability-based, as I understand it!)