aWsm
gc
Our great sponsors
aWsm | gc | |
---|---|---|
3 | 43 | |
282 | 911 | |
5.0% | 2.5% | |
4.9 | 9.4 | |
about 1 month ago | 10 days ago | |
C | WebAssembly | |
BSD 3-clause "New" or "Revised" License | 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.
aWsm
-
Web Assembly OS guidance
Thanks, tonight I will look at the wasmi runtime and aWsm runtime.
-
Plugin mechanism: dynamic loading, bytecode or scripting?
Have a small bytecode runtime. I've been looking at micro wasm runtimes, but the footprint is way above what I can afford (awasm, wasmtime);
- Wasm3 compiles itself (using LLVM/Clang compiled to WASM)
gc
-
Bring garbage collected programming languages efficiently to WebAssembly
It may take some time for WasmGC to be usable by .NET. Based on the discussions the first version of WasmGC does not have a good way to handle a few .NET specific scenarios, and said scenarios are "post-post-mvp". [0]
My concern, of course, is that there is not much incentive for those features to be added if .NET is the only platform that needs them... at that point having a form of 'include' (to where a specific GC version can just be cached and loaded by another WASM assembly) would be more useful, despite the pain it would create.
The WASM GC support is intentionally kept as simple as possible, see https://github.com/WebAssembly/gc/blob/main/proposals/gc/MVP... . Building a "universal" or "generic" VM supporting many languages on an equally seamless basis is explicitly not a goal of WASM-GC; it is expected that each implementation might require its own hacks on top of the basic support WASM provides, but this is okay because FFI/cross-language interop is seen as an entirely separate issue.
-
WasmGC – Compile and run GC languages such as Kotlin, Java in Chrome browser
Yes, that's definitely true: a single GC will not be optimal for everything, or even possible. Atm interior pointers are not supported at all, for example, but they are on the roadmap for later:
https://github.com/WebAssembly/gc/blob/main/proposals/gc/Pos...
What launched now is enough WasmGC to support a big and useful set of languages (Java, Kotlin, Dart, OCaml, Scheme), but a lot more work will be required here!
-
Learn WebAssembly by writing small programs
GC proposal is from 2018: https://github.com/WebAssembly/proposals/issues/16 and there’s code: https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...
Seems like an awefully long time for progress to be made, given all the possibilities it would unlock.
-
The state of modern Web development and perspectives on improvements
First is the size. Writing a server-side and client-side program is possible with Rust, and the resulting WASM package will be small enough. At the same time, Microsoft Blazor converts C# code to WASM, but the client delivery has to include the reduced .NET runtime, taking several megabytes for a script. The same is true for GoLang, even with an attempt to reduce the runtime delivery in TinyGo WASM. Developers want to work with their favorite languages, whether it is Java, Kotlin, Dart, C#, F#, Swift, Ruby, Python, C, C++, GoLang, or Rust. These languages produce groups of runtimes. For example, JVM and .NET have many common parts, Ruby and Python are dynamically interpreted at runtime, and all mentioned depend on automatic garbage collection. For smaller WASM packages, browser vendors can include extended runtime implementations, for example, by delivering a general garbage collector as part of WASM. Garbage collection support by WASM is currently in progress: WASM GC, .NET WASM Notes.
-
Douglas Crockford: “We should stop using JavaScript”
My understanding is that the main limitation is technical. WASM doens't do GC or the host system calling conventions and cannot interact directly with object from Javascript because of this. However, this is being worked[0] on and will be solved eventually. Even without this the performance overhead of bridging to JS is low enough that WASM frameworks can beat out React.
0: https://github.com/WebAssembly/gc/blob/main/proposals/gc/Ove...
-
Blazor United - When it ships it would be the most glorious way to do web with .NET
The .net team has given their notes on it, the concern is more on the memory layout from what I remember. Though it may be possible still. The runtime would likely still ship some gc code, but only a subset for cases not supported by the wasm gc itself and a few more for interfacing with the gc service, which overall should still result on smaller payloads compared to current sizes.
-
Kernel-WASM: Sandboxed kernel mode WebAssembly runtime for Linux
I assume that's one of the parts of the work done at https://github.com/WebAssembly/gc - not happening any soon yet, but it'll eventually be done.
-
Out of the loop: WASM for non-web projects
To be fair, there is a GC proposal and some runtimes might even already be working on it, but as of today we have no WASM runtime that handles garbage collection.
-
WebAssembly: Docker Without Containers
Actually, Wasm goes into the direction you are pointing. A Wasm runtime should add a little overhead to the requirements of the Wasm module.
However, it's true Wasm is not on that point yet. There are open threads about deallocate Wasm memory [1]. However, I expect these features, as well as Garbage Collection [2] will come to the stardard over time. This will allow modules and runtimes to properly manage memory usage.
What are some alternatives?
dotnet-webgl-sample - .NET + WebAssembly + WebGL = 💖
wasm3 - 🚀 A fast WebAssembly interpreter and the most universal WASM runtime
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Mono - Mono open source ECMA CLI, C# and .NET implementation.
simd - Branch of the spec repo scoped to discussion of SIMD in WebAssembly
v86 - x86 PC emulator and x86-to-wasm JIT, running in the browser
wasmer-python - 🐍🕸 WebAssembly runtime for Python
interface-types
teavm - Compiles Java bytecode to JavaScript, WebAssembly and C
WASI - WebAssembly System Interface
meetings - WebAssembly meetings (VC or in-person), agendas, and notes