memory-control
stringref
| memory-control | stringref | |
|---|---|---|
| 5 | 2 | |
| 19 | 34 | |
| - | - | |
| 0.0 | 0.0 | |
| over 1 year ago | about 1 year 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.
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
stringref
-
Extism Makes WebAssembly Easy
The idea of Wasm as a universal plugin system is very promising. But string passing is maybe not the best example to highlight, considering that Wasm is introducing stringref to enable zero-copy string sharing between the Wasm runtime and host language.
https://github.com/WebAssembly/stringref/blob/main/proposals...
-
The Risks of WebAssembly
> dcodeIO (from the AssemblyScript community) was definitely not behaving in good faith
I certainly disagree with that take. I only see one person being frustrated because his concerns were being thrown under the rug as "non important", I would recommend you to read on dcode's blog to learn more about how the timeline happened [1]. There are always things to improve regarding how we communicate, of course, but those should not be used as a weapon to attack or dismiss someone but as means to improve.
It's also important to note that a few months after, the Wasm committee realized of the mistake and actually tried to solve it with the Wasm Stringref proposal [2].
The issue is not about if using UTF-8 or UTF-16 is the way to go, but how disagreement is being handled in what's supposed to be an open community
[1] https://dcode.io/#webassembly
[2] https://github.com/WebAssembly/stringref
What are some alternatives?
multi-memory - Multiple per-module memories for Wasm
modsurfer - Devtools to validate, audit and investigate WebAssembly binaries.
asm-dom - A minimal WebAssembly virtual DOM to build C++ SPA (Single page applications)
js-string-builtins - JS String Builtins
sycamore - A library for creating reactive web apps in Rust and WebAssembly
component-sandbox-demo
wajic - WebAssembly JavaScript Interface Creator
crypto - Cryptographic operations in WASM, C, Typescript for Nodejs and the browser.
interface-types
awesome-wasm-runtimes - A list of webassemby runtimes
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
AnswerOverflow - Indexing Discord Help Channel Questions into Google