|3 months ago||3 days ago|
|Apache License 2.0||Apache License 2.0|
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.
Cranelift's Instruction Selector DSL, ISLE: Term-Rewriting Made Practical
2 projects | /r/rust | 21 Jan 2023
Hey if the parsing was the annoying part, how about this? https://github.com/vickenty/lang-c
Prettier $20k Bounty was Claimed
16 projects | news.ycombinator.com | 27 Nov 2023
The roadmap I linked above. The WASI folks have done a poor job at communicating, no doubt, but I'm surprised someone like yourself literally building a competitor spec isn't following what they are doing closely.
Just for you I did some googling: see here for the current status of WASI threads overall, or here and here for what they are up to with WASI in general. In this PR you can see they enabled threads (atomic instructions and shared memory, not thread creation) by default in wasmtime. And in this repository you can see they are actively developing the thread creation API and have it as their #1 priority.
If folks want to use WASIX as a quick and dirty hack to compile existing programs, then by all means, have at it! I can see that being a technical win. Just know that your WASIX program isn't going to run natively in wasmtime (arguably the best WASM runtime today), nor will it run in browsers, because they're not going to expose WASIX - they're going to go with the standards instead. so far you're the only person I've met that thinks exposing POSIX fork() to WASM is a good idea, seemingly because it just lets you build existing apps 'without modification'.
Comical you accuse me of being polarizing, while pushing for your world with two competing WASI standards, two competing thread creation APIs, and a split WASM ecosystem overall.
Spin 2.0 – open-source tool for building and running WASM apps
13 projects | news.ycombinator.com | 4 Nov 2023
Thanks for the question!
Spin could definitely run in more places than what we have pre-built binaries for. Specifically, we could run on all platforms Wasmtime supports today (https://github.com/bytecodealliance/wasmtime/releases/tag/v1...), including RISC and S390X, for example.
And while we have been experimenting a bit with running Spin on RISC, we haven't really had the bandwidth or requirement to build a production build for those yet.
Are you interested in a specific operating system or CPU architecture? Would love to understand your scenario.
Dave Cutler: The Secret History of Microsoft Windows [video]
2 projects | news.ycombinator.com | 22 Oct 2023
> I used to think we'd eventually get to capability based security, but now I see we'll always be stuck with application permission flags, the almost worthless bastard cousin, instead.
My hope is that WASI will introduce capability based security to the mainstream on non-mobile computers  - it might just take some time for them to get it right. (And hopefully no half-baked status-quo-reinforcing regressive single—runtime-backed alternatives win in the meantime.)
Requiem for a Stringref
4 projects | news.ycombinator.com | 19 Oct 2023
WasmTime finished finished the RFC for the implementation details in June: https://github.com/bytecodealliance/wasmtime/issues/5032
Should You Be Scared of Unix Signals?
8 projects | news.ycombinator.com | 16 Oct 2023
MongoDB’s New Query Engine
4 projects | news.ycombinator.com | 21 Sep 2023
re LLVM: Yes, Cranelift was designed to address these issues
Val, a high-level systems programming language
10 projects | news.ycombinator.com | 18 Jul 2023
No longer does Wasm/WASI need JS host! There are many spec-compliant runtimes built for environments from tiny embedded systems up to beefy arm/x86 racks:
- https://github.com/extism/extism (disclaimer, my company's project - makes wasm easily embeddable into 16+ programming languages!)
Announcing Floneum (A open source graph editor for local AI workflows written in rust)
3 projects | /r/rust | 12 Jul 2023
Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI
Sandboxing C++, Rust, Python Code?
5 projects | /r/rust | 9 Jul 2023
Look into Web Assembly and wasmer or wasmtime.
Creating a simple sandboxed language
3 projects | /r/LLVM | 4 Jul 2023
What are some alternatives?
wasmer - 🚀 The leading WebAssembly Runtime supporting WASIX, WASI and Emscripten
SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.
wasm3 - 🚀 A fast WebAssembly interpreter and the most universal WASM runtime
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
wazero - wazero: the zero dependency WebAssembly runtime for Go developers
PyO3 - Rust bindings for the Python interpreter
trunk - Build, bundle & ship your Rust WASM application to the web.
mold - Mold: A Modern Linker 🦠
pybind11 - Seamless operability between C++11 and Python