mnemonik

7 ms·

1.
Making WebAssembly and Wasmtime More Portable(bytecodealliance.org)
3 points by mnemonik 2y ago|0 comments
2.
New Stack Maps for Wasmtime and Cranelift(bytecodealliance.org)
3 points by mnemonik 2y ago|0 comments
3.
by mnemonik 3y ago
Yes, you can use the component model (and other tooling like WIT) without using WASI. Yes, the component model is a standard developed under the umbrella of the W3C's WebAssembly Community Group. That said, while it is relatively stabl
4.
by mnemonik 4y ago
There is a section in the linked announcement titled "Why use a WebAssembly Runtime?" that hopefully answers your question.
5.
Security and Correctness in Wasmtime(bytecodealliance.org)
77 points by mnemonik 4y ago|16 comments
6.
Wasmtime 1.0: A Look at Performance(bytecodealliance.org)
99 points by mnemonik 4y ago|22 comments
7.
by mnemonik 7y ago
Both Wasmtime and Lucet can AOT compile Wasm, for what it's worth.
8.
by mnemonik 8y ago
There is a DOM story: host bindings. It just isn't implemented yet. However, that doesn't mean that you can't use it now. wasm-bindgen is essentially a polyfill for host bindings plus some other little things. Some resources
9.
How does dynamic dispatch work in WebAssembly?(fitzgeraldnick.com)
98 points by mnemonik 8y ago|19 comments
10.
by mnemonik 8y ago
GNU libiberty includes a Rust symbol demangler that you can link: https://github.com/gcc-mirror/gcc/blob/master/libiberty/rust...
11.
Speed Without Wizardry(fitzgeraldnick.com)
206 points by mnemonik 9y ago|69 comments
12.
by mnemonik 9y ago
Great catch -- thanks for reporting this! Fix is over in https://github.com/fitzgen/source-map-mappings/pull/15
13.
by mnemonik 9y ago
Thanks for the heads up. It used to be a `thread_local!`, but switching to a `static mut` resulted in smaller code size. I just forgot to update the code snippet in the article. > which IIRC requires unsafe access as it's not thread
14.
by mnemonik 9y ago
Thanks for the report! We've already fixed some of these issues[0] but I didn't update the code snippets in the article -- woops! [0] https://github.com/tromey/vlq/commit/3b41a2b6c778ce476eaaa28...
15.
Oxidizing Source Maps with Rust and WebAssembly(hacks.mozilla.org)
207 points by mnemonik 9y ago|30 comments
16.
How Stylo Brought Rust and Servo to Firefox(bholley.net)
639 points by mnemonik 9y ago|191 comments
17.
by mnemonik 10y ago
.eh_frame is DWARF with a couple tiny tweaks
18.
by mnemonik 10y ago
There is some discussion about power usage in this video by Jack Moffit: https://www.youtube.com/watch?list=PL4sEzdAGvRgCYXot-o5cVKOo...
19.
by mnemonik 10y ago
Quantum wiki page with info on how to get involved: https://wiki.mozilla.org/Quantum
20.
In which a spacefaring text editor holds up against an onslaught(technomancy.us)
3 points by mnemonik 10y ago|0 comments
21.
Browsers, Innovators Dilemma, and Project Tofino(medium.com)
13 points by mnemonik 10y ago|0 comments
22.
by mnemonik 11y ago
I think these are the slides: http://pcwalton.github.io/slides/webrender-talk-022016/
23.
Compiling to WebAssembly: It’s Happening(hacks.mozilla.org)
306 points by mnemonik 11y ago|216 comments
24.
by mnemonik 11y ago
Yup, a patch is in review right now: https://bugzilla.mozilla.org/show_bug.cgi?id=960780 Not sure if you missed it in the parent post, but here is a sneak peek: http://i.imgur.com/qjWOERs.gif
25.
by mnemonik 11y ago
Can you file bug(s) with links to the crash report(s) in about:crashes? Alternatively, you could email me your crash reports (email in profile) and I could file bug(s) for youe.
26.
by mnemonik 11y ago
Up until a couple months ago, it had an O(n^2) marking algorithm that kept iterating until it got to a fixed point. Thanks to the hard work of Steve Fink, these days it has an O(n) marking algorithm. See https://bugzilla.mozilla.
27.
by mnemonik 11y ago
Yes, it can be enabled all the time with about:config -> privacy.trackingprotection.enabled = true
28.
by mnemonik 11y ago
Yes it is. I also wrote more about the backend implementation on lobste.rs < https://lobste.rs/s/cvtz0x/firefox_s_new_memory_tool >: Hi folks, For the last year or so, my coworker Jim Blandy and I have been
29.
Two paths, one peak: a view on high-performance language implementations(wingolog.org)
9 points by mnemonik 11y ago|0 comments
30.
Developer Edition 44: New visual editing and memory management tools(hacks.mozilla.org)
7 points by mnemonik 11y ago|0 comments

More ›