Our great sponsors
WinObjC | WASI | |
---|---|---|
8 | 45 | |
6,229 | 4,513 | |
0.1% | 3.1% | |
0.0 | 7.0 | |
over 1 year ago | 23 days ago | |
C | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
WinObjC
-
HelloSystem – OS with original Mac philosophy with a modern architecture
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
-
Emulating an iPod Touch 1G and iPhoneOS 1.0 using QEMU (Part I)
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.
-
I love Swift but I don't use it
sometime u just need to use that search input field. https://github.com/microsoft/WinObjC
-
Is the Windows Bridge for iOS Projects Dead?
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)
WASI
-
WASI 0.2.0 and Why It Matters
Sadly, still no Framebuffer API for WASI GUI apps (https://github.com/WebAssembly/WASI/issues/174).
WASI Co-chair here. Nothing in WASI is "somehow blocked by Google", or indeed blocked by anyone at all. Graphics support in WASI hasn't been developed simply because nobody has put energy into developing graphics support in WASI.
At the end of 2023 we counted around 40 contributors who have been working on WASI specifications and implementations: https://github.com/WebAssembly/meetings/blob/main/wasi/2023/... . That is a great growth for our project from a few years ago when that issue was filed, but as you can see from what people are working on, its all much more foundational pieces than a graphics interface. Also, if you look at who is employing those contributors, its largely vendors who are interested in WASI in the context of serverless. That doesn't mean WASI is limited to only serverless, but that has been the focus from contributors so far.
By rolling out WASI on top of the WASM Component Model we have built a sound foundation for creating WASI proposals that support more problem domains, such as embedded systems (@mc_woods and his colleagues are helping with this), or graphics if someone is interested in putting in the work. Our guide to how to create proposals is found here: https://github.com/WebAssembly/WASI/blob/main/Contributing.m... .
-
Missing the Point of WebAssembly
> As I understand it, it's not even really possible today to make WebAssembly do anything meaningful in the browser without trampolining back out to JavaScript anyway, which seems like a remarkable missed opportunity.
That's the underlying messy API it's built on. There are specs to make the API more standardized like https://github.com/WebAssembly/WASI
But overall, yeah, it feels like a shiny new toy everyone is excited about and wants to use. Some toys can be fun to play with, but it doesn't mean we have to rewrite production systems in it. Sometimes, or most of the time, toys don't become useful tools.
-
Running WASI binaries from your HTML using Web Components
Snapshot Preview 1 is the standard all tools are building to right now. The specification is available here: https://github.com/WebAssembly/WASI/blob/main/legacy/preview...
It's pretty unreadable though!
Preview 2 looks like it will be a big change, and is just being finalised at the moment. I'd expect that when preview 2 is available there will be an improvement in the quality of documentation. I'm not sure how long it will take after release for tools to start switching to it. I'd expect Preview 1 will still be the main target at least for the rest of this year.
-
WASI: WebAssembly System Interface
I've never seen a worse-described project than WASI.
"Component model interfaces always support link-time interposition."
Like WTF does this mean? The README tells me nothing. I click on docs and there's one file.
https://github.com/WebAssembly/WASI/blob/main/docs/WitInWasi...
Wit? Never heard of it. I click on "legacy" and I see preview0 and preview1, which are even more poorly-written specs.
Wikipedia tells me WASI is a POXIS-like interface, but with POSIX, I know exactly where to look up the functions. Where's the WASI spec?
I'll be honest - this whole project feels like candy for architecture astronauts and goes against the spirit of WebAssembly.
Looks at how well-written WebAssembly's goals are: https://webassembly.org/docs/high-level-goals/. Their spec is easy to find and easy to read. This is what I want from WASM.
Whatever WASI is doing I don't like it. And neither does AssemblyScript team for the record: https://www.assemblyscript.org/standards-objections.html.
> Like WTF does this mean? The repo tells me nothing
Directly above the sentence you quoted:
"Interposition in the context of WASI interfaces is the ability for a Webassembly instance to implement a given WASI interface, and for a consumer WebAssembly instance to be able to use this implementation transparently. This can be used to adapt or attenuate the functionality of a WASI API without changing the code using it."
> and I've still yet to see a clear write-up about what WASI is.
In the same document: [0]
> WTF is wit?
The first link in that document ("Starting in Preview2, WASI APIs are defined using the Wit IDL.") is [1].
> I click on "legacy" and I see preview0 and preview1, which are basically unreadable proto-specs.
The README for the legacy directory [2] clearly explains what they are.
> Where's a single well-written WASI spec?
"Development of each API happens in its own repo, which you can access from the proposals list." [3]
> Whatever WASI is doing, I don't like it.
Clearly not - you've gone out of your way to ignore all of the documentation that answers your questions.
> And neither does AssemblyScript team apparently
The AssemblyScript team have a bone to pick with WASI based on their misunderstanding of what WASI is for (it is not intended for use on the web) and WASI's disinterest in supporting UTF-16 strings. You can see for yourself in [4].
[0]: https://github.com/WebAssembly/WASI/tree/main#wasi-high-leve...
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
We are excited to contribute back to Wasmtime and the component model, as well as to new projects and proposals emerging in this space (such as new Wasm proposals, like WASI Preview 2, wasi-keyvalue, wasi-sql or wasi-cloud).
-
The Tug-of-War over Server-Side WebAssembly
I've been reading the following repositories.
-
Create Elegant C++ Spatial Processing Pipelines in WebAssembly
Since that time, Emscripten's capabilities have advanced and been standardized with WebAssembly (Wasm) in the Web Platform. Moreover, Wasm's scope has expanded dramatically with the advent of the WebAssembly System Interface, WASI, and The Component Model.
What are some alternatives?
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
webgpu-wgsl-hello-triangle - An example of how to render a triangle with WebGPU using WebGPU Shading Language - the "Hello world!" of computer graphics.
threads - Threads and Atomics in WebAssembly
wasi-libc - WASI libc implementation for WebAssembly
node-sqlite3 - SQLite3 bindings for Node.js
gpuweb - Where the GPU for the Web work happens!
wasm-micro-runtime - WebAssembly Micro Runtime (WAMR)
wasmtime - A fast and secure runtime for WebAssembly
stevenarella - Multi-protocol Minecraft-compatible client written in Rust
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
extism - The framework for building with WebAssembly (wasm). Easily load wasm modules, move data, call functions, and build extensible apps.