scale
workers-wasi
scale | workers-wasi | |
---|---|---|
5 | 5 | |
464 | 119 | |
3.0% | 0.0% | |
8.5 | 0.0 | |
4 days ago | about 1 year ago | |
C | C++ | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" 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.
scale
-
WASM by Example
This is exactly one of the use-cases for the Scale Framework[1]. (Disclaimer: I work on this project)
You can absolutely take a library from one language and run it in another. In a sense, you could kind of see this ability as drastically reducing the need for rewriting sdks, middlewares, etc. across languages, as you could just reuse code from one language across many others. We played around with some fun ideas here, like taking a Rust regex library and using it in a Golang program via a scale function plugin (compiled to Wasm), to the effect of the performance being ~4x faster than native code that uses Go's regex library.
[1] https://github.com/loopholelabs/scale
- Show HN: Scale – Serverless functions, in any language, powered by WASM
- Show HN: Write Language-agnostic functions with WebAssembly you can use
-
Announcing Scale: A WebAssembly runtime for running Go functions in any other language
We're currently working on a couple of different projects, but everything we've launched so far (fRPC and Scale) is FOSS.
workers-wasi
-
WASM by Example
The examples seemed clear enough to read (I did not test them), but I felt than even when teaching by example there needs to be more overview and explanation. I.e., I would prefer an overview of WASM structure and use with examples, rather than just the examples. (I have some (but limited) experience using WASM.)
As for the utility of wasm, note also that Cloudflare workers can run WASM on edge servers [1], and that the Swift community has some support for compiling to wasm [2].
I've never really understood how wasm could do better than java bytecode, but I've been impressed with how much people are using lua and BPF. More generally, in a world of federated programming, we need languages client can submit that providers can run safely, without obviously leaking any secret sauce -- perhaps e.g., for model refinement or augmented lookup.
[1] https://github.com/cloudflare/workers-wasi
-
SQLite builds for WASI since 3.41.0
Those are great questions! I believe Emscripten will be required for some cases as it provides more features for targeting a Web Browser. If WASI is the only requirement for a Wasm module, then there are three possible solutions:
- Use a library that provides the WASI bindings in a browser environments: there are some OSS projects that provides WASI bindings on top of browser technologies. For example, workers-wasi from Cloudflare [1]. It could be even another Wasm module that provides the implementation for the main one. I know the people from Loophole Labs are experimenting with virtual filesystems (VFS) [2].
- Browsers provides a WASI implementation: server-oriented runtimes like NodeJS are already providing these bindings (under a experimental flag). I shouldn't have stated that as a fact, as browsers may provide it or not. However, I saw in the past the Google Chrome team experimenting with WASI and the browser FileSystem API [3]. So, I think it may happen :)
- [1] https://github.com/cloudflare/workers-wasi
- [2] https://www.youtube.com/watch?v=46jZSXVxYPw
- [3] https://github.com/GoogleChromeLabs/wasi-fs-access
-
The Tug-of-War over Server-Side WebAssembly
Indeed, some people are doing this:
- WASI once had an official polyfill https://wasi.dev/polyfill/, now apparently succeeded by https://github.com/bjorn3/browser_wasi_shim
- wasmer-js provides a JS polyfill for WASI https://docs.wasmer.io/integrations/js/wasi
- Cloudflare has a WIP polyfill https://github.com/cloudflare/workers-wasi
I'm generally leery of non-temporary polyfills, so I'm not sure that any of these feel like a long-term viable option for me.
-
Rust advocacy at a medium-sized startup
I think modern C++ could be perfectly viable as well. Maybe https://github.com/cloudflare/workers-wasi would be a good starting point? I'm not too knowledgeable on the subject. Exciting times though, I think WASM might be the great equalizer.
-
Store SQLite in Cloudflare Durable Objects
While there is a WASI implementation for Workers: cloudflare/workers-wasi, I prefer to implement each import manually - especially when there are so few and especially while I am still experimenting. This helps me to keep the full picture of what's going on.
What are some alternatives?
excelize-wasm - A WebAssembly build of the Go Excelize library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
workers-rs - Write Cloudflare Workers in 100% Rust via WebAssembly
olin - Webassembly + Event Sourcing
asyncify - Standalone Asyncify helper for Binaryen
plugin-XDCC - 📁 XDCC for webircgateway
wasm-sqlite - [Experimental] SQLite compiled to WASM with pluggable page storage.
cup - Git Contribution Automation
binaryen - Optimizer and compiler/toolchain library for WebAssembly
lagon - Deploy Serverless Functions at the Edge. Current status: Alpha
do-sqlite - [Experimental] Persist SQLite in a Cloudflare Durable Object
yatas-template - Template for creating a plugin for YATAS
wasi-libc - WASI libc implementation for WebAssembly