hangover
memory-control
| hangover | memory-control | |
|---|---|---|
| 33 | 5 | |
| 1,232 | 19 | |
| - | - | |
| 8.6 | 0.0 | |
| 16 days ago | over 1 year ago | |
| Dockerfile | WebAssembly | |
| GNU Lesser General Public License v3.0 only | 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.
hangover
- Hangover 9.0 – Runs simple Windows 32-bit (x86) applications on ARM64 Linux
- Release hangover-8.21 · AndreRH/hangover
- Hangover 8.21 – runs simple Win32 applications on ARM64 Linux
- Hangover-8.15
- Hangover 0.8.5 runs simple Win64/Win32 applications on arm64/ppc64le/x86_64 Linux and x86_64 Mac
- Hangover 0.8.5 Released
- The Tug-of-War over Server-Side WebAssembly
memory-control
-
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.
-
The Tug-of-War over Server-Side WebAssembly
Additionally, googlers are championing memory control https://github.com/WebAssembly/memory-control/blob/main/prop..., which provides memory protection.
-
How do Rust WebAssembly apps free unused memory?
But researching it a bit I found this issue, so it clearly seems to be a problem for a bunch of people out there. And apparently both V8 and Spidermonkey have already addressed this quite recently, see this issue.
-
WebAssembly and C++
FWIW there is a proposal in the works to add page-based protection, which will allow unmapping the 0 page, restoring the trap-on-null-deref behavior that is important for many languages with safety checks.
https://github.com/WebAssembly/memory-control
What are some alternatives?
box64 - Box64 - Linux Userspace x86_64 Emulator with a twist, targeted at ARM64 Linux devices
multi-memory - Multiple per-module memories for Wasm
box86 - Box86 - Linux Userspace x86 Emulator with a twist, targeted at ARM Linux devices
asm-dom - A minimal WebAssembly virtual DOM to build C++ SPA (Single page applications)
FEX - A fast usermode x86 and x86-64 emulator for Arm64 Linux
sycamore - A library for creating reactive web apps in Rust and WebAssembly
RPi4 - Raspberry Pi 4 UEFI Firmware Images
wajic - WebAssembly JavaScript Interface Creator
design - WebAssembly Design Documents
interface-types
wasi-threads
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly