hanez

5 ms·

1.
by hanez 8mo ago
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 refcounted with atomic ops. The host doesn’t need to lock anyt
2.
by hanez 8mo ago
• 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 point of view. • Lifetime is managed with plain reference coun
3.
by hanez 8mo ago
• 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. • Yes: shared‑memory primitives are the “escape hatch”
4.
by hanez 8mo ago
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 me for an account on https:/
5.
by hanez 8mo ago
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 sure if this
6.
by hanez 8mo ago
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. Concurrency and data exchange happen via message passing an
7.
by hanez 8mo ago
You're welcome! Would love to get some feedback!
8.
Fun 0.37.62 – The programming language that makes you have fun(fun-lang.xyz)
2 points by hanez 8mo ago|14 comments
9.
by hanez 8mo ago
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), but there are differences. Influenced by Bash, C, Lua, PHP, Py
10.
by hanez 11y ago
Uh, he ist not a bot, he is not a bot, he is not a bot... :D
11.
by hanez 11y ago
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.
by hanez 11y ago
Exactly this is what the original post is about... ;)
13.
by hanez 11y ago
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 Rump Kernel at http://rumpkernel.org/ is in
14.
by hanez 11y ago
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 software stack on top. Take a look
15.
by hanez 11y ago
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 to implement the OS stuff - It's done already. May I a
16.
by hanez 11y ago
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 everything. It was just the first file that came
17.
by hanez 11y ago
Uh, wow! That was it! Thanks for this answer...
18.
by hanez 11y ago
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... :|
19.
by hanez 11y ago
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 (lines starting with '#') in my .zs
20.
First pass at ads to try to fund some new flypray developers(github.com)
1 points by hanez 11y ago|0 comments
21.
My Future of Developing Firefox Add-Ons(chrisfinke.com)
1 points by hanez 11y ago|0 comments
22.
All Colours Are Beautiful(acab.muc.ccc.de)
2 points by hanez 16y ago|0 comments