tail-call
memory64
| tail-call | memory64 | |
|---|---|---|
| 4 | 7 | |
| 106 | 178 | |
| 0.0% | 1.7% | |
| 3.8 | 8.5 | |
| about 1 year ago | 9 days ago | |
| WebAssembly | WebAssembly | |
| 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.
tail-call
-
Top 8 Recent V8 Updates
Support for tail-calls to perform tail-call optimizations.
-
Kernel-WASM: Sandboxed kernel mode WebAssembly runtime for Linux
https://news.ycombinator.com/item?id=32069418
https://github.com/WebAssembly/tail-call/issues/15#issuecomm...
- WebAssembly Tail Calls moved to Phase 4, soon enabled by default in Chrome
- Tail calls for native targets
memory64
-
Top 8 Recent V8 Updates
A completed implementation of memory64 for memory-hungry applications.
-
Extism Makes WebAssembly Easy
Indeed, webassembly is moving extremely slowly. I started a project years ago expecting https://github.com/WebAssembly/memory-control/blob/main/prop... and https://github.com/WebAssembly/memory64 to be fixed at some point. Neither are yet, and the project still suffers from it to this day.
I think wasm is still great without these fixes, but I have lost confidence in the idea that wasm will reach its full potential any time soon.
-
How Photoshop solved working with files larger than can fit into memory
It's in the works: https://github.com/WebAssembly/memory64
Starting with 32bit had some performance advantages because 64bit runtimes can use virtual memory shenanigans to implement bounds checking with zero overhead. In wasm64 they'll have to do explicit bounds checking instead.
-
Transformers.js
Right - currently, everything runs using WASM (32-bit, with 64-bit coming soon [1,2]), and I plan to add support for WebGPU soon!
(WebGPU is the successor to WebGL, which is coming out in April 2023 [3])
[1] https://github.com/WebAssembly/memory64/issues/36#issuecomme...
-
What was the rational for 32-bit memory addresses in WebAssembly? It seems very short-sighted, considering it only came out pretty recently in 2017
It shouldn't be a big surprise that a 64-bit pointer extension is out there and being worked on. The great thing about a VM is you can integrate major changes like this when they are needed and with the benefit of experience and hindsight. If the 4GB limit turns out to be restrictive then it can be lifted.
- Why Am I Excited About WebAssembly?
-
Increasing Smart Contract Canister Memory Proposal is live for review
The goal of this proposal is to increase the amount of memory that canisters can access [eventually] bound only by the actual capacity of the subnet. Since, the Memory64 proposal is not standardized 1 yet and its implementation 1 in Wasmtime is not production ready yet, this proposal enables the increase by introducing a new stable memory API.
What are some alternatives?
simd - Branch of the spec repo scoped to discussion of SIMD in WebAssembly
interface-types
kernel-wasm - Sandboxed kernel mode WebAssembly runtime.
wasmtime - A fast and secure runtime for WebAssembly
exception-handling - Proposal to add exception handling to WebAssembly
botnet - Multiplayer programming game using Rust and WebAssembly
temporal-polyfill - A lightweight polyfill for Temporal, successor to the JavaScript Date object
proposal-temporal - Provides standard objects and functions for working with dates and times.
component-sandbox-demo
reference-types - Proposal for adding basic reference types (anyref)
quickjs-emscripten - Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions
spark-nlp - State of the Art Natural Language Processing