Live data from Hacker News

Viewing profile — mavdol04

mavdol04

HN member
Joined
Fri, Jan 24, 2025, 12:40 AM UTC
HN karma
179
Public activity
52 items

About mavdol04

No profile information was provided.

Recent public activity

  1. comment
    Comment #48583986

    It doesn't have browser support yet because it's WASI-based, so there are a few more steps compared to Emscripten (two different ways to build for WebAssembly). But networking is s…

  2. comment
    Comment #48582052

    With RISC‑V emulation we get the virtual hardware components we need to boot Linux like MMU, registers etc. So a GCC WASM backend could definitely help, but I'm not sure it could r…

  3. story
    Show HN: Vpod – Tiny Linux sandbox running in WASM

    Hi HN, I spent the last few months reading the RISC‑V specification to build the lightest possible sandboxes. The idea behind a vpod is to quickly spin up a Linux sandbox from snap…

  4. story
    WASI 0.3

    https://github.com/WebAssembly/WASI/releases/tag/v0.3.0

  5. comment
    Comment #48381642

    It's a bit of a cheat, but you can hit 0.00% every time. Just measure the bar length, then cross-multiply. :) Example: bar is 1250px, max is 2100, number is 376 → (1250 × 376) / 21…

  6. comment
    Comment #48207533

    Working on a RISC-V emulator targeting Wasm. Is RVV 1.0 stable enough to be worth implementing, or would Zve32f/Zve64d already cover most use cases ?

  7. comment
    Comment #48153251

    That's cool, i did exactly the same few years ago

  8. comment
    Comment #48009633

    Nice, what are you building exactly ?

  9. story
    Show HN: Capsule Bash – Sandboxed Bash for Agents

    I've always felt that existing Bash wasn't adapted for agents. It gives way too much freedom and not enough feedback to enrich the context after each command. I ended up building t…

  10. comment
    Comment #47961033

    I am in the EU timezone and had some minor issues recently with GitHub as well, but it never lasts very long.

  11. story
  12. comment
    Comment #47853073

    The worst that could happen is having your credentials stolen. It’s an LLM architectural flaw, so it has to be at the tools level so the only way to prevent it is still sandboxing …

  13. story
  14. comment
    Comment #47462721

    I think a shared array just avoids the copy, not the serialization which is the main problem as they showed with serde-wasm-bindgen test

  15. comment
    Comment #47443637

    Wait, you just invented a reverse CAPTCHA for AI agent

  16. comment
    Comment #47397099

    That’s great, but it can’t be used in production because it’s not available for Linux (so no AWS, no GCP, etc.) and requires Docker Desktop. Still nice for experimenting, though.

  17. comment
    Comment #47379489

    I mean standardizing on an x86 subset would replace wasm's native portability with a kind of 'emulated' compatibility, and this is one of wasm's strengths. If we do that, non-x86 h…

  18. story
  19. comment
    Comment #46907046

    It actually works a bit differently. The eval is executed by the interpreter running inside the isolated wasm sandbox (StarlingMonkey). You can think of it as each sandbox having i…

  20. comment
    Comment #46875071

    Thanks! Not yet, but that's a great idea. I could definitely add it to the roadmap.

  21. comment
    Comment #46874359

    yeah, the previous example was quite basic. I will write a complete example for that, but here is how you can run dynamic code: import { task } from "@capsule-run/sdk"; export defa…

  22. comment
    Comment #46874013

    I would love for the component model tooling to reach that level of maturity. Since the runtime uses standard WASI and not Emscripten, we don't have that seamless dynamic linking y…

  23. comment
    Comment #46873471

    Thanks for the feedback! What do you think about running the separate file directly from the decorator?

  24. comment
    Comment #46873326

    Thanks! Got it, I will add more examples for that. Currently you can do both: run dynamically untrusted code with eval, or run fully encapsulated logic (like in the existing exampl…

  25. comment
    Comment #46872927

    I understand your point. I added native Python support because C extensions will eventually become compatible. Also, we might see more libraries built with Rust extensions appearin…