stateroom
wasmer
stateroom | wasmer | |
---|---|---|
4 | 131 | |
134 | 17,829 | |
1.5% | 1.2% | |
5.0 | 9.9 | |
1 day ago | 1 day ago | |
Rust | Rust | |
MIT License | MIT 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.
stateroom
- Hey Rustaceans! Got a question? Ask here (12/2023)!
-
Launch HN: Drifting in Space (YC W22) – A server process for every user
In the case of containers it gets tricky because of how it interacts with the scheduler (e.g. if a node is idle but has a bunch of paused containers that could be unpaused at any time, the scheduler has to decide how to proceed), but I love the concept. It's something I've thought a bit about in a world where the server can be compiled to WebAssembly, because it's imaginable to suspend it and serialize the memory state so that it can be sent off to storage somewhere and pulled out when the next request comes in. This was actually part of the motivation behind a library I wrote called Stateroom (https://github.com/drifting-in-space/stateroom), which creates a stateful WebSocket server as a WebAssembly module, but I haven't yet implemented the ability to freeze the state of the module between requests.
-
Use Phoenix Channels
> "just drop it in and it just works" for self hosted websocket systems
I was also been underwhelmed by options in this area, so I've been working on a Rust library called Jamsocket[1]. The idea is that all you need to do is implement a trait, overload the functions for the events you want to handle (new connection, message, etc.) and deploy it.
I still need to work on production aspects of it, but it's in a state where you can play with it for local development, so I figured I'd share it here in case any Rust developers want to tinker with it.
[1] https://github.com/jamsocket/jamsocket
wasmer
-
Bebop v3: a fast, modern replacement to Protocol Buffers
This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )
-
Unlocking the Power of WebAssembly
WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.
-
Show HN: dockerc – Docker image to static executable "compiler"
Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...
As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.
[0]: https://github.com/ktock/container2wasm
[1]: https://wasmer.io/
- RustPython
-
Howto: WASM runtimes in Docker / Colima
I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.
-
Show HN: Mutable.ai – Turn your codebase into a Wiki
Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer
Looking forward to seeing the results :)
- Jaq – A jq clone focused on correctness, speed, and simplicity
-
Prettier $20k Bounty was Claimed
The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]
Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!
Keep up the great work!!
[1] https://github.com/biomejs/biome/issues/720
[2] https://wasmer.io/
[3] https://wasix.org/
-
The Curse of Docker
It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.
That's the main reason Wasmer [1] was created :)
[1] https://wasmer.io
-
Bring garbage collected programming languages efficiently to WebAssembly
Thanks for the mention to Wasmer.
I'll put here a link in case is useful for future readers: https://wasmer.io/
What are some alternatives?
spawner - Session backend orchestrator for ambitious browser-based apps. [Moved to: https://github.com/drifting-in-space/plane]
wasmtime - A fast and secure runtime for WebAssembly
falcon - Brushing and linking for big data
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.
Sandstorm - Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
wasm3 - 🚀 A fast WebAssembly interpreter and the most universal WASM runtime
bitque - A simplified Jira clone built with seed.rs and actix
quickjs-emscripten - Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
lucet - Lucet, the Sandboxing WebAssembly Compiler.
awesome-wasm-runtimes - A list of webassemby runtimes
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript