Wasi-libc Alternatives

wasi-libc reviews and mentions

• You Are Already Using Wasm In Production
  1 project | dev.to | 9 Dec 2024

  WebAssembly has a set of extended interfaces collectively called the WebAssembly System Interface (WASI). This bit is chugging its way through standardization, due to be finalized in 2025. But if there is one thing we should have collectively learned from the standardization of HTML, CSS, HTTP, JavaScript, and onward, standards-based implementations often stabilize and reach production readiness far sooner than the standards body can walk its lumbering gate to a final ratification. While WASI continues to add new interfaces, the core interfaces (components, file system, environments, and so on) have long been stable, and have long been deployed into production.

• Hyperlight: Virtual machine-based security for functions at scale
  4 projects | news.ycombinator.com | 7 Nov 2024
• Sqlite3 WebAssembly
  20 projects | news.ycombinator.com | 15 Oct 2024

  https://wasi.dev/

  wow I didn't know this was a thing. thanks for filling me in!

• Is the Web Browser the Most Important Platform for App Development?
  6 projects | dev.to | 3 Oct 2024

  Standardization Efforts: Projects like WASI aim to create an ABI standard that facilitates better integration between WebAssembly and the host operating system. However, WASI’s full browser support, especially for web-specific APIs like WebGPU, is still a work in progress.

• I am curious. How many of you work on a windows system?
  2 projects | /r/developersIndia | 9 Dec 2023

  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?
  2 projects | /r/typst | 7 Dec 2023

  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
  9 projects | news.ycombinator.com | 14 Nov 2023

  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
  6 projects | news.ycombinator.com | 30 May 2023

  Actually, it was in wasi-libc: https://github.com/WebAssembly/wasi-libc/blob/main/libc-bott...

• Valheim: Regarding Mods
  2 projects | /r/Games | 29 May 2023

  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
  3 projects | news.ycombinator.com | 29 May 2023

  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

• A note from our sponsor - SaaSHub
  www.saashub.com | 12 Jan 2025

  SaaSHub helps you find the best software and product alternatives Learn more →