bifrost
wasi-libc
bifrost | wasi-libc | |
---|---|---|
10 | 48 | |
518 | 803 | |
1.5% | 2.4% | |
9.6 | 7.7 | |
6 days ago | 4 days ago | |
Go | C | |
Apache License 2.0 | 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.
bifrost
-
Bifrost: A peer-to-peer communications engine with pluggable transports
Disagree :) Having a `examples/` or `demo/` directory is already good enough, and this repository even has one of those too! https://github.com/aperturerobotics/bifrost/tree/master/exam...
One of the examples seems relatively easy to grasp if you're a web developer, about how to do HTTP forwarding: https://github.com/aperturerobotics/bifrost/blob/master/exam...
- Are We Wasm Yet - Part 1
-
Open source Go projects to contribute (beginners)
I'm the creator of, and looking for contributors + early adopters of https://github.com/aperturerobotics/bifrost - check it out!
- Communicating with Quic-over-WebSocket using Bifrost and libp2p
-
Bifrost: cross-platform modular p2p comms library & daemon for Go
Demo: SSH over Xbee radios: https://github.com/aperturerobotics/bifrost/blob/master/examples/ssh-xbee-forwarding/ssh-xbee-forwarding.org
-
oniongrok: Onion addresses for anything.
Have a look at Bifrost and libp2p - which also address peers by public keys, and multiplex protocols over transports. Bifrost specifically is an attempt to improve code re-use and modularity/easy configuration of each component.
- Bifrost: modular framework w/ transports, links, streams, pubsub (NATS), encryption, sim, quic-over-websocket in the browser
- Bifrost: cross-platform modular P2P communications engine released
wasi-libc
-
I am curious. How many of you work on a windows system?
Now there are projects like WASI that allows for interfacing with system resources for WASM code this allows for devs to target WASM runtime for their apps sliding the apps to run locally on any OS without any porting required. This could be a game changer in the future like Docker and containers was in the past decade.
-
How to select some elements from array randomly?
So it doesn’t seem like there has been progress on a pseudo-random number generator function for typst, but there are multiple other ways to solve this: 1. Just don’t. Typst has this functional philosophy, there one input always produces the same output. (not an answer to your question tho) 2. Interface with a webassembly module which has a random number generator. So you could e.g. compile c to wasm and statically link a libc version. You would then just have to export the rand() function. (You could use any lang for this, which has a stdlib with a pseudo random number generator) 3. Implement your own. Random number generators are actually not that hard something like an LCG isn’t to complex. (Id provide an example but im on my phone rn)
-
Lapce Editor v0.3 Released
Actually WASI[0] will be a better alternative, IIRC extism serialize and deserialize the data that you want to pass every time, adding a lot of overhead.
[0] https://wasi.dev
-
Wasix, the Superset of WASI Supporting Threads, Processes and Sockets
Actually, it was in wasi-libc: https://github.com/WebAssembly/wasi-libc/blob/main/libc-bott...
-
Valheim: Regarding Mods
Proper isolation in C# is only now becoming a thing, with .Net support for WASI, which is essentially a WebAssembly sandbox which can be given extremely granular privileges (such as access to spefic file system directories, or an effective virtual file system). As an upside, the idea is that it should be possible to write the WASI packages in more or less anything.
-
Hardening Drupal with WebAssembly
Wasm Labs dev here :)
In mod_wasm, there are some differences with a pure CGI implementation. When Apache boots, it loads the configuration and initializes the WasmVM. When a new HTTP request arrives, the VM is ready so you don't need to initialize a different process to manage it.
You still need to process the request and pass the data to the Wasm module. This step is done via STDIN through the WebAssembly System Interface (WASI) implementation [0]. The same happens in the opposite direction, as the module returns the data via STDOUT.
So, the CGI pattern is still there, but it doesn't require new processes and all the code runs in a sandbox.
However this is not the only way you can run a Wasm module. In this specific case, we use CGI via WASI. In other cases, you may compile a module to fulfill a specific API, like ProxyWasm [1] to create HTTP filters for proxies like Envoy.
- [0] https://wasi.dev/
- [1] https://github.com/proxy-wasm/spec
-
Compile emacs to wasm?
Never done that, but I think you need this: https://wasi.dev/
-
Extending web applications with WebAssembly and Python
The Python builds from the WebAssembly language runtimes [0] project target the WebAssembly System Interfaces (WASI) [1]. It allows the Python interpreter to interact with resources like the filesystem.
Many server-side Wasm runtimes supports WASI out of the box. For the browser, you need to provide a polyfill to emulate these resources like the one provided by the WASI team [2].
Regarding SQLite, these builds include libsqlite so you should be able to use it :)
- [0] https://github.com/vmware-labs/webassembly-language-runtimes
- [1] https://wasi.dev/
- [2] https://wasi.dev/polyfill/
-
How to Debug WASI Pipelines with ITK-Wasm
Effective debugging results in effective programming; itk-wasm makes effective debugging of WebAssembly possible. In this tutorial, adapted from the itk-wasm documentation, we walk through how to debug a C++ data processing pipeline with the mature, native binary debugging tools that are comfortable for developers. This is a fully featured way to ensure the base correctness of a processing pipeline. Next, we will walk through an interactive debugging experience for WASI WebAssembly. With itk-wasm, we can debug the same source code in either context with an interactive debugger. We also have a convenvient way to pass data from our local filesystem into a WebAssembly (Wasm) processing pipeline.
-
Running Go code inside a NodeJS app with WASM (Part 1/2, 2023)
Communication between the WASM module and the rest of the application needs to be done in very simple types (bytes, ints and floats). No complex types are supported yet. This is why most WASM compilers also provide some glue-code to map between complex types like strings or arrays. The Web Assembly System Interface (WAS) is an on-progress standard aimed to solve this last limitation; once it's mature it will allow easy interoperation with almost every environment. WASI is already available in some WSAM compilers and runtimes.
What are some alternatives?
hackpad - The in-browser IDE for Go
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
gio - Mirror of the Gio main repository (https://git.sr.ht/~eliasnaur/gio)
wasi-sdk - WASI-enabled WebAssembly C/C++ toolchain
gdg - Grafana Dashboard Manager
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
msgp - A Go code generator for MessagePack / msgpack.org[Go]
wasmtime - A fast and secure runtime for WebAssembly
rueidis - A fast Golang Redis client that supports Client Side Caching, Auto Pipelining, Generics OM, RedisJSON, RedisBloom, RediSearch, etc. [Moved to: https://github.com/redis/rueidis]
WASI - WebAssembly System Interface
dsq - Commandline tool for running SQL queries against JSON, CSV, Excel, Parquet, and more.
binaryen - Optimizer and compiler/toolchain library for WebAssembly