RReverser

11 ms·

61.
by RReverser 5y ago
No, that's never allowed - that's the strength of Wasm. Any unchecked helpers are for language-level semantic blocks within Wasm memory itself, not for leaving the sandbox. So worst case you might override and corrupt your own dat
62.
Show HN: An adapter for using Rust and Rayon with WebAssembly threads(github.com)
1 points by RReverser 6y ago|0 comments
63.
by RReverser 6y ago
> already uncommon It's definitely not uncommon though. Just to provide one example: how often do you use all the arguments to `.map` callback? Usually you'd write something like `arr.map(x => x + 1)`. However, to spell out
64.
by RReverser 6y ago
I guess you'd have to make series of patches to GDB to make it work, as well as to build your own DevTools extension once the API is stable, but in theory should be possible, yeah.
65.
by RReverser 6y ago
Did you mean ChromeDevSummit talk or there was a separate WebSummit talk on this too?
66.
by RReverser 6y ago
You will be able to build your own extension with any backend in the future, but I'm curious what you're looking to gain from that? I don't know whether GDB understands the Wasm-specific constructs in DWARF, while the current
67.
by RReverser 6y ago
Thanks, going to fix soon-ish! Not sure how it slipped by.
68.
by RReverser 6y ago
It does work with basic Rust compiled to Wasm, but most of the ecosystem uses wasm-pack / wasm-bindgen, which currently doesn't support DWARF. You can subscribe to https://github.com/rustwasm/wasm-bindgen&#x2F
69.
by RReverser 6y ago
Interesting, are you on the latest Chrome Canary? If so, could you please report a bug with a simple repro to the https://bugs.chromium.org/p/chromium/issues/entry?template=D... link mentioned in the article?
70.
by RReverser 6y ago
> Answering my own question, a little, I use figma.com a lot. But the potential seems so great, and the available PWAs so poor.... It's just that WebAssembly, like any new technology, can and usually is used in very specific paths t
71.
by RReverser 6y ago
CSS is Turing complete.
72.
by RReverser 6y ago
Yep. It's a new API that other browsers haven't implemented yet.
73.
Show HN: WebAssembly in a browser with access to a real filesystem(wasi.rreverser.com)
2 points by RReverser 6y ago|2 comments
74.
by RReverser 6y ago
<meme>why not both?</meme>
75.
by RReverser 6y ago
Video recording showing some features: https://www.youtube.com/watch?v=qRmO-8b4WmE&feature=youtu.be
76.
WebAssembly in a browser with access to a real filesystem(wasi.rreverser.com)
3 points by RReverser 6y ago|3 comments
77.
Debugging memory leaks in WebAssembly using Emscripten(web.dev)
1 points by RReverser 6y ago|0 comments
78.
by RReverser 6y ago
I wonder if this was the same developer who asked the question back on 31st of December 2018 on whether it's okay to use Internet Archive’s Wayback Machine as a CDN: https://webmasters.stackexchange.com/questions&#x2F
79.
Bringing OxiPNG to Squoosh(rreverser.com)
1 points by RReverser 6y ago|0 comments
80.
by RReverser 8y ago
Not sure if someone else mentioned it already, but you actually can play with it for free on https://cloudflareworkers.com/ . Sure, it's a limited version without binding to a specific domain and, correspondingly, witho
81.
by RReverser 8y ago
> at the end of the day it is still an AST interpreter In a pretty remote sense, I guess. > One possibility is that you are passing around the operands to your filters as Rust lexically-closed values instead of using a custom stack fo
82.
by RReverser 8y ago
This is not executed on packets (like it would be in Wireshark), but rather on requests defined in the application layer as a set of properties.
83.
by RReverser 8y ago
Hmm, your examples seem to show pretty fine grained control over moves / borrows?
84.
by RReverser 8y ago
In general I agree that Rc could've been nice to copy instead of cloning explicitly, but on another hand I'm a pretty big opponent of having "lots of Arcs and Rcs" since they usually hide the ownership and data flow, and
85.
by RReverser 8y ago
Oh, sure, if you're willing to go to unsafe techniques, you can go straight to a template JIT as well. But, for us, the balance is important, and safety is probably even more important than further wins in performance (which we can sti
86.
by RReverser 8y ago
It's not a big issue when you're working on the code continuously, thanks to the incremental compilation, but in general I'd always take slower compilation with more analysis (== lower risk of crashes and faster runtime) over
87.
by RReverser 8y ago
All of these were written by different people, and languages are quite different as well, so not sure that particular aspect played a role.
88.
by RReverser 8y ago
More control is, as usual, less ability for automatic optimisations. For example, Rust uses knowledge of tag + data combinations for niche-filling enums where possible (and more similar optimisations to come), while LLVM can use this inform
89.
by RReverser 8y ago
After looking into it, I think I actually did come across it long time ago. As you've noted, the approaches are different, but it's indeed inspiring in the sense of moving to safer languages for parsing in general.
90.
by RReverser 8y ago
> as you're no longer directly tied to the AST of the input language This is the case with closure-based approach too, and indeed was one of the main motivations to switch away from AST interpretation.

More ›