team
cloudlibc
team | cloudlibc | |
---|---|---|
3 | 1 | |
1,404 | 290 | |
0.0% | 0.0% | |
0.0 | 10.0 | |
over 4 years ago | over 3 years ago | |
C | ||
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
team
-
The Tug-of-War over Server-Side WebAssembly
Further down that GitHub issue, it mentions the problem has been fixed:
* https://github.com/rust-lang/rust/issues/71871#issuecomment-...
* https://github.com/rust-lang/rust/pull/79998
Weirdly though, there's another issue (opened prior) that's ongoing and seems to indicate things aren't fixed after all:
* https://github.com/rustwasm/team/issues/291
-
Rust mod team resignation
As for all the rust-wasm stuff, the dispute makes little sense. The "opposition" wants her to transfer publishing rights to a Github group actively being sunsetted and portraying it as a power struggle, yet this struggle is taking place in an issue Williams started in an effort to transfer ownership. Based on the last comments, it looks like publishing rights have been distributed to other members so the whole narrative is effectively moot.
-
rust / emscripten / wasm / opengl / sdl2 / porting..
I don't have direct WebAssembly experience (So far, my projects have either required stuff not compatible with WASI or been DOM-centric "must degrade gracefully with JavaScript disabled" stuff) but this thread looks like a good starting point for answering that question.
cloudlibc
-
The Tug-of-War over Server-Side WebAssembly
Deep respect to the CloudABI folks, a project inspired the WASI ideas:
> CloudABI is no longer being maintained. It was an awesome experiment, but it never got enough traction to be sustainable. If you like the idea behind CloudABI, please consider looking into the WebAssembly System Interface (WASI). WASI's design has been inspired by CloudABI.
https://github.com/NuxiNL/cloudlibc
What are some alternatives?
wasi-threads
TSC - The Node.js Technical Steering Committee
hangover - Hangover runs simple Win32 applications on arm64 Linux
browser_wasi_shim - A WASI shim for in the browser
memory-control - A proposal to introduce finer grained control of WebAssembly memory.
workers-wasi
noah - Bash on Ubuntu on macOS
team - Rust teams structure