reference-types
mediacapture-record
Our great sponsors
reference-types | mediacapture-record | |
---|---|---|
9 | 3 | |
151 | 101 | |
- | - | |
5.3 | 2.6 | |
over 2 years ago | 12 months ago | |
WebAssembly | Bikeshed | |
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.
reference-types
-
Old CSS, new CSS (2020)
> It could be an interesting use case for WASM if the problem of passing data into the WASM VM cheaply (perhaps by reference) can be solved.
WASM Reference Types should hopefully solve this. The WASM working group seems to have some good momentum - so I'm hopeful this (or a similar replacement spec) will land sooner rather than later.
https://github.com/WebAssembly/reference-types/blob/master/p...
-
Bring garbage collected programming languages efficiently to WebAssembly
AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:
- reference types: https://github.com/WebAssembly/reference-types/blob/master/p...
- interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...
- component model: https://github.com/WebAssembly/component-model
If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
-
Extism: Make all software programmable with WebAssembly
[1]: https://github.com/WebAssembly/proposals
A glance of the overview and spec seems to indicate that WASM will provide some primitive data types, and any GC language can build their implementation on top of it. As I understand it, it's heavily based on Reference Types[3], which allows acting on host-provided types, and is already considered part of the spec [4]. It doesn't remove the need for the 5 different runtimes to have their own GC, but it lowers the bulk that the runtimes need to carry around, and offloads some of that onto the WASM runtime instead.
[3]: https://github.com/WebAssembly/reference-types/blob/master/p...
-
Struggling to find yew benchmarks
They've talked about interface types, and added reference types, which is a stepping stone toward the GC extension proposal, which would be a stepping stone toward manipulating the DOM from the WebAssembly side, but their official roadmap page is more short-term.
-
Blazor WASM and privacy
Nope, WASM reference types, it has nothing to do with .NET type system.
-
FFmpeg for browser and node, powered by WebAssembly
> And there's been talk of exposing the JS GC to wasm for a few years. Hopefully when that stuff lands, it'll get easier to marshal objects across the gap.
You don't need a Wasm GC to do this. If you only need js objects to pass on to, say, the host's function or check is null or not, then reference types that are opaque external references: https://github.com/WebAssembly/reference-types/blob/master/p...
You can even do many more things if you export `Reflect` to WebAssembly: https://github.com/AssemblyScript/assemblyscript/blob/main/t...
Reference Types are available almost everywhere already (In Safari will be available after 15.0): https://webassembly.org/roadmap
- WebContainers: Run Node.js natively in the browser
-
Cranelift, Part 3: Correctness in Register Allocation
Re: GC -- yes, indeed, the whole business with safepoints arose from the need to support Wasm reference types as a backend for Wasmtime or Firefox. No safepoints are needed for Rust (or other C-like) code.
-
Wasmer 1.0 released, the fastest WebAssembly VM, cross-compilation, headless, native object engine, AOT compilers and more!
Reference Types,
mediacapture-record
-
How do I Effectively Capture Video playing in Canvas?
Courtesy of this GitHub thread, my currently working, but very inconvenient strategy to capture the video is to use mediaCapture(0) on the canvas element with MediaStreamTrackProcessor to pipe frames into WebM muxer from a package called webm-muxer.
-
How to create a seamless loop for a looping video?
WebRTC's RTCRtpSender.replaceTrack() method achieves "seamless" replacement of a MediaStreamTrack. I proposed the same be added to MediaRecorder, see Add replaceTrack method to MediaRecorder., Add replaceStream to MediaRecorder.
-
FFmpeg for browser and node, powered by WebAssembly
I guess this could be used to remux the broken files that are spitted by the MediaRecorder API, which have missing metadata that prevents from seeking and thus far has been ignored / sweeped away in Chrome [1], Firefox [2], and even the standard itself [3], which ignored in its design the basic fact that encoding any file should include a "closing" stage (where metadata is written) before yielding it as a finished file.
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=642012
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1283464
[3]: https://github.com/w3c/mediacapture-record/issues/119
What are some alternatives?
assemblyscript - A TypeScript-like language for WebAssembly.
wasmtime - A fast and secure runtime for WebAssembly
rust-ffmpeg-wasi - ffmpeg libraries precompiled for WebAsembly/WASI, as a Rust crate.
ffmpeg.wasm - FFmpeg for browser, powered by WebAssembly
MediaFragmentRecorder - Record media fragments
proposals - Tracking WebAssembly proposals
mediacapture-transform - MediaStreamTrack Insertable Media Processing using Streams
schism - A self-hosting Scheme to WebAssembly compiler
tinyglitch - Just an experiment with libavformat/libavcodec
webcontainer-core - Dev environments. In your web app.
biwascheme - Scheme interpreter written in JavaScript