Live data from Hacker News

Viewing profile — mazieres

mazieres

HN member
Joined
Mon, Apr 06, 2015, 8:13 PM UTC
HN karma
459
Public activity
44 items

About mazieres

[ my public key: https://keybase.io/dmazieres; my proof: https://keybase.io/dmazieres/sigs/3DmoKVq1V_7ujh0cmZZ1ZHCcl1razm-Iwkwyh5mPX9A ]

Recent public activity

  1. comment
    Comment #47569531

    An AI agent that works 99.9% of the time is a lot more dangerous than one that works 90% of the time, because the former leads to expectations of 100% safe behavior. I've never bee…

  2. comment
    Comment #47569499

    Please use a dev container! Empirically, a lot of people don't, and some people regularly enable YOLO mode on their actual laptops. So if you've never run a code assistant outside …

  3. comment
    Comment #47569455

    jai uses persistent file systems for your changes (except for `/tmp`, `/var/tmp` and `/run/user`, which usually aren't persistent anyway). The data is stored under `$HOME/.jai` by …

  4. comment
    Comment #47569395

    But there is an old-school README.me at the github homepage: https://github.com/stanford-scs/jai The repository has an old-school ASCII INSTALL file. If you don't like the vitepres…

  5. comment
    Comment #47558053

    Yes, unpacking a tar file is much safer than piping arbitrary code to bash! You can look at the PKGFILE in the directory--it is only 30 lines long and mostly variable assignments. …

  6. comment
    Comment #47558011

    You can do that, but you need root to set it up each time, and it's not super convenient--you need to decide in advance which user account you are going to work under, and you may …

  7. comment
  8. comment
    Comment #47551990

    Yes, people very much are, and that's exactly the problem! People run `claude --dangerously-skip-permissions` and `codex --yolo` all the time. And I think one of the appeals of ope…

  9. comment
    Comment #47551836

    Also, a lot of people use multiple harnesses. I'm often switching between claude, codex, and opencode. It's kind of nice to have the sandbox policy independent of the actual AI ass…

  10. comment
    Comment #47551642

    What distro are you using? The only two dependencies are libacl and libmount. I'm trying to figure out which distros don't include these by default, and if the libraries are really…

  11. comment
    Comment #47551493

    Human author here. The fact that I don't know web design shouldn't detract from my expertise in operating systems. I wrote the software and the man page, and those are what really …

  12. comment
    Comment #47551370

    I've seen claude get confused about what directory it's in. And of course I've seen claude run rm -rf *. Fortunately not both at the same time for me, but not hard to imagine. The …

  13. comment
    Comment #47551317

    The problem is that in practice, many people don't take the flamethrower to the shed. I recently had a conversation with someone who was arguing that you don't really need jai beca…

  14. comment
    Comment #47551256

    It's a good point. Maybe I should add an option to make certain directories read-only even under the current working directory, so that you can make .git/ read-only without moving …

  15. comment
    Comment #47550283

    What would it take for people to stop recklessly running unconstrained AI agents on machines they actually care about? A Stanford researcher thinks the answer is a new lightweight …

  16. story
  17. comment
    Comment #39546301

    Your constexpr function is not legal because it doesn't initialize all the array elements, even though the compiler might let you get away with it. That's easily fixed. More import…

  18. comment
    Comment #39532782

    Actually not. Try to implement a compile-time initialized const char* that represents some compile-time value like sizeof(X) for some data structure X. You'll see that you need rec…

  19. comment
    Comment #39532689

    What is your non-template function in this example?

  20. comment
    Comment #39527617

    Obviously there's a whole section on comma folds that you didn't read. However, more importantly, there are things that you can't do without recursion. For example, how would you i…

  21. comment
    Comment #26233139

    Wow, that talk is a fantastic link. He actually gets negative overhead from using coroutines, because the compiler has more freedom to optimize when humans don't prematurely break …

  22. comment
    Comment #26222997

    Oh, that must be a typo in the document, sorry. I just fixed it. The actual corodemo.cc file was correct, though: http://www.scs.stanford.edu/~dm/blog/corodemo.cc Also, here's a mo…

  23. comment
    Comment #26222953

    > Stackless means when you resume a coroutine you're still using the same OS thread stack This is confusing, because it begs the question "same as what?" In fact, you can migrate a…

  24. comment
    Comment #26222697

    Agreed. I think the killer use is for event-driven programs that already do a lot of "stack ripping". If you are already manually putting all your "local" variables into an object …

  25. comment
    Comment #26222655

    You are right that you are effectively stuck in a single coroutine (non-stack) frame. But you can chain multiple such coroutine frames, because one coroutine can co_await another.