WASI | node | |
---|---|---|
45 | 944 | |
4,634 | 104,274 | |
2.3% | 1.2% | |
6.9 | 9.9 | |
8 days ago | 5 days ago | |
Rust | JavaScript | |
GNU General Public License v3.0 or later | 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.
WASI
-
WASI 0.2.0 and Why It Matters
WASI Co-chair here. Nothing in WASI is "somehow blocked by Google", or indeed blocked by anyone at all. Graphics support in WASI hasn't been developed simply because nobody has put energy into developing graphics support in WASI.
At the end of 2023 we counted around 40 contributors who have been working on WASI specifications and implementations: https://github.com/WebAssembly/meetings/blob/main/wasi/2023/... . That is a great growth for our project from a few years ago when that issue was filed, but as you can see from what people are working on, its all much more foundational pieces than a graphics interface. Also, if you look at who is employing those contributors, its largely vendors who are interested in WASI in the context of serverless. That doesn't mean WASI is limited to only serverless, but that has been the focus from contributors so far.
By rolling out WASI on top of the WASM Component Model we have built a sound foundation for creating WASI proposals that support more problem domains, such as embedded systems (@mc_woods and his colleagues are helping with this), or graphics if someone is interested in putting in the work. Our guide to how to create proposals is found here: https://github.com/WebAssembly/WASI/blob/main/Contributing.m... .
- WASI Launching Preview 2
-
Missing the Point of WebAssembly
> As I understand it, it's not even really possible today to make WebAssembly do anything meaningful in the browser without trampolining back out to JavaScript anyway, which seems like a remarkable missed opportunity.
That's the underlying messy API it's built on. There are specs to make the API more standardized like https://github.com/WebAssembly/WASI
But overall, yeah, it feels like a shiny new toy everyone is excited about and wants to use. Some toys can be fun to play with, but it doesn't mean we have to rewrite production systems in it. Sometimes, or most of the time, toys don't become useful tools.
-
Running WASI binaries from your HTML using Web Components
Snapshot Preview 1 is the standard all tools are building to right now. The specification is available here: https://github.com/WebAssembly/WASI/blob/main/legacy/preview...
It's pretty unreadable though!
Preview 2 looks like it will be a big change, and is just being finalised at the moment. I'd expect that when preview 2 is available there will be an improvement in the quality of documentation. I'm not sure how long it will take after release for tools to start switching to it. I'd expect Preview 1 will still be the main target at least for the rest of this year.
-
WASI: WebAssembly System Interface
> Like WTF does this mean? The repo tells me nothing
Directly above the sentence you quoted:
"Interposition in the context of WASI interfaces is the ability for a Webassembly instance to implement a given WASI interface, and for a consumer WebAssembly instance to be able to use this implementation transparently. This can be used to adapt or attenuate the functionality of a WASI API without changing the code using it."
> and I've still yet to see a clear write-up about what WASI is.
In the same document: [0]
> WTF is wit?
The first link in that document ("Starting in Preview2, WASI APIs are defined using the Wit IDL.") is [1].
> I click on "legacy" and I see preview0 and preview1, which are basically unreadable proto-specs.
The README for the legacy directory [2] clearly explains what they are.
> Where's a single well-written WASI spec?
"Development of each API happens in its own repo, which you can access from the proposals list." [3]
> Whatever WASI is doing, I don't like it.
Clearly not - you've gone out of your way to ignore all of the documentation that answers your questions.
> And neither does AssemblyScript team apparently
The AssemblyScript team have a bone to pick with WASI based on their misunderstanding of what WASI is for (it is not intended for use on the web) and WASI's disinterest in supporting UTF-16 strings. You can see for yourself in [4].
[0]: https://github.com/WebAssembly/WASI/tree/main#wasi-high-leve...
-
A Gentle Introduction to WebAssembly
The Bytecode Alliance initiated a sub-project called the WebAssembly System Interface (WASI). WASI is an API that allows WebAssembly access to system features such as files, filesystems, Berkeley sockets, clocks, and random numbers. WASI acts as a system-level interface for WebAssembly, so incorporating a runtime into a host environment and building a platform is easier.
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
We are excited to contribute back to Wasmtime and the component model, as well as to new projects and proposals emerging in this space (such as new Wasm proposals, like WASI Preview 2, wasi-keyvalue, wasi-sql or wasi-cloud).
-
The Tug-of-War over Server-Side WebAssembly
I've been reading the following repositories.
https://github.com/WebAssembly/WASI/blob/main/Proposals.md
node
-
How to set up a new project using Yarn
Let’s see how we could set up a shiny new JavaScript project using the Yarn package manager. We are going to set up nodenv, install Node.js and Yarn, and then initialize a new project that we will then be able to use as a foundation for our further ideas.
-
Qu'est-ce qu'un projet MERN Stack et comment créer une application CRUD avec? Partie 2/2, Tutoriel
Node.js ( https://nodejs.org/ )
- WebSockets com Socket.io: Criando Aplicações Real-Time com Node.js
-
Day 2: Setting Up Angular Development Environment
Visit the Node.js website and download the latest version of Node.js for your operating system.
-
How to Add Firebase Authentication To Your NodeJS App
Basic knowledge of Node.js and its environment setup. If you don't have Node.js installed on your system, make sure you download and install it from the official Node.js website.
-
Part 2: Setting Up Your Node.js Environment
Node.js can be easily installed from its official website. Depending on your operating system, you can choose the Windows, macOS, or Linux version. Node.js packages come with npm (Node Package Manager), which is essential for managing dependencies in your projects.
-
Announcing Node.js 22.0.0: What’s New and Why It Matters
To get started with Node.js 22.0.0, you can download the latest version from the official Node.js website. For those upgrading from an older version, it is recommended to test your existing applications for compatibility with the new release, particularly if you are using native modules or rely heavily on third-party npm packages.
-
How to Make a VS Code Extension Using TypeScript: A Step-by-Step Guide
Node.js (version 10 or higher)
-
Getting Started with Next.js: Part 1 - Setting Up Your Project
Before we start, ensure that you have Node.js installed on your computer. This is necessary because we will use Node's package manager (npm) to create our Next.js project. If you need to install Node.js, you can download it from the official Node.js website.
-
How to create a react project from scratch
Before starting a new project in react, you need to make sure that you have NodeJS install on your system. You can download the latest version of node at https://nodejs.org. Follow the instructions on the node website to do the installation.
What are some alternatives?
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Svelte - Cybernetically enhanced web apps
webgpu-wgsl-hello-triangle - An example of how to render a triangle with WebGPU using WebGPU Shading Language - the "Hello world!" of computer graphics.
widevine-l3-decryptor - A Chrome extension that demonstrates bypassing Widevine L3 DRM
threads - Threads and Atomics in WebAssembly
source-map-resolve - [DEPRECATED] Resolve the source map and/or sources for a generated file.
wasi-libc - WASI libc implementation for WebAssembly
sharp-libvips - Packaging scripts to prebuild libvips and its dependencies - you're probably looking for https://github.com/lovell/sharp
node-sqlite3 - SQLite3 bindings for Node.js
nodejs.dev - A redesign of Nodejs.org built using Gatsby.js with React.js, TypeScript, and Remark.
gpuweb - Where the GPU for the Web work happens!
hashlips_art_engine - HashLips Art Engine is a tool used to create multiple different instances of artworks based on provided layers.