bnjbvr

4 ms·

1. 1.▲
   Bytecode Alliance: Building a secure by default, composable future for wasm(bytecodealliance.org)

   23 points by bnjbvr 7y ago|1 comments
2. 2.▲
   Improving My GitHub Workflow(blog.benj.me)

   2 points by bnjbvr 7y ago|0 comments
3. 3.▲
   Async Stack Traces in Rust(fitzgeraldnick.com)

   3 points by bnjbvr 7y ago|0 comments
4. 4.▲
   Standardizing WASI: A system interface to run WebAssembly outside the web(hacks.mozilla.org)

   434 points by bnjbvr 8y ago|231 comments
5. 5.▲
   by bnjbvr 8y ago

   Good find! At the moment it is very very experimental and you might experience crashes and slowdowns if you're using it in place of the regular flags (that is why it is enabled only on Nightly builds and will not be enabled on Beta&#x2
6. 6.▲
   by bnjbvr 8y ago

   We've had optimizations to make wasm -> JS calls fast for a long time, and they became even slightly faster (around 10 or 15%) last year. There is a proposal to add DOM integration within wasm, so one could import DOM functions in w
7. 7.▲
   by bnjbvr 9y ago

   For what it's worth, the name is obviously a pun and a small wink to the Graal VM [1]. Not sure there's any intention to reference TempleOS's HolyC. [1] https://github.com/graalvm/
8. 8.▲
   by bnjbvr 9y ago

   There's a brainfuck [1] interpreter example in the examples/ directory, which I assume is the reason for this allegedly temporary name. [1] https://en.wikipedia.org/wiki/Brainfuck