bitque
stateroom
Our great sponsors
| bitque | stateroom | |
|---|---|---|
| 1 | 4 | |
| 18 | 134 | |
| - | 3.0% | |
| 0.0 | 5.0 | |
| about 1 year ago | 10 days ago | |
| Rust | Rust | |
| Mozilla Public License 2.0 | 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.
bitque
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
What are some alternatives?
nbody-wasm-sim - An N-body WebAssembly simulation using Web GPU
spawner - Session backend orchestrator for ambitious browser-based apps. [Moved to: https://github.com/drifting-in-space/plane]
wasm-pdf - Generate PDF files with JavaScript and WASM (WebAssembly)
falcon - Brushing and linking for big data
localghost - Ergonomic Rust bindings to the Web platform
Sandstorm - Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.
rust-wasm-on-lambda-edge - Rust/WASM on AWS Lambda@Edge (CloudFront)
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
wasm-learning - Building Rust functions for Node.js to take advantage of Rust's performance, WebAssembly's security and portability, and JavaScript's ease-of-use. Demo code and recipes.
lucet - Lucet, the Sandboxing WebAssembly Compiler.
astro-nannou-starter - A minimal boilerplate for Astro / Vite with the Nannou creative framework (Rust → WASM). Supports multiple sketches + hot-reload.
wasmtime - A fast and secure runtime for WebAssembly