Live data from Hacker News

Viewing profile — hanez

hanez

HN member
Joined
Wed, Mar 03, 2010, 12:24 PM UTC
HN karma
13
Public activity
23 items

About hanez

No profile information was provided.

Recent public activity

  1. comment
    Comment #46796938

    We don’t expose shared mutability to VMs. The trick is: publish‑as‑immutable plus adoption via ports. Ports/queues do the synchronization; fun_shared_buffer is off‑heap and refcoun…

  2. comment
    Comment #46796842

    • We default to isolates for safety and scaling. • Zero‑copy sharing is done with fun_shared_buffer, an off‑heap, GC‑untracked, pointer‑free block that’s immutable from the VM’s po…

  3. comment
    Comment #46796797

    • Yes: isolated state (one VM per embed) is usually the right default. It avoids global locks (e.g., a GIL), makes scheduling simpler, and keeps failure/lifetime boundaries crisp. …

  4. comment
    Comment #46789859

    I need to say, that issues can be opened at https://github.com/hanez/fun/issues , but I do not develop Fun on GitHub. Pull requests will not be accepted there. Send patches or ask …

  5. comment
    Comment #46789639

    I added a section to https://git.xw3.org/fun/fun/src/branch/main/docs/internals.m... that describes this more detailed. I copied from other documents some seconds ago and I am not …

  6. comment
    Comment #46789460

    I chose isolated state (like Lua) rather than a single global lock (like Python’s GIL). Each VM has its own heap, scheduler, and garbage collection. There are no cross-VM pointers.…

  7. comment
    Comment #46787926

    You're welcome! Would love to get some feedback!

  8. comment
    Comment #46787332

    What is Fun? Fun is an experiment, just for fun, but Fun works! Fun is a highly strict programming language, but also highly simple. It looks like Python (My favorite language), bu…

  9. story
  10. comment
    Comment #10744257

    Uh, he ist not a bot, he is not a bot, he is not a bot... :D

  11. comment
    Comment #10742008

    That clarified the difference! Thank you. I think I mixed rump kernel and rumprun. I saw a talk long time ago and am not very deep into that nowadays. Therefore, double thanks!

  12. comment
    Comment #10741739

    Exactly this is what the original post is about... ;)

  13. comment
    Comment #10741659

    I believe to get this production ready will take some years. From what I understand in the projects FAQ page they want to implement the concept of a Unikernel and this is what the …

  14. comment
    Comment #10741577

    What they want to do is to implement the concept of a unikernel ( https://en.wikipedia.org/wiki/Unikernel ). That's a very different approach then running a complete OS with their …

  15. comment
    Comment #10741553

    Sounds a little bit crazy to me at first but when thinking about it, it is a nice idea. May you should take a look at Rump Kernels and build your stuff on top. Then you do not need…

  16. comment
    Comment #10725382

    Yes, I am aware of that but I wanted to understand the usage of 'look' at this point. It was a fault to try stuff using the .zshrc file at first because I ran into misunderstanding…

  17. comment
    Comment #10725349

    Uh, wow! That was it! Thanks for this answer...

  18. comment
  19. comment
    Comment #10725249

    When sorting the file first I get no output anymore: sort ~/.zshrc -o /tmp/.zshrc look "#" /tmp/.zshrc Sorry for the noise but I am confused... :|

  20. comment
    Comment #10725210

    When running 'look' to get all comments in a file I only get the first found line in the ouput. Can someone explain this? look "#" .zshrc There are really a lot more comments (line…

  21. story
  22. story
  23. story