managarm VS Vale

managarm is pretty clean from what I remember.

Somewhat related, Managarm[0] also attempts to be Linux compatible, but has a microkernel, multiserver design.

0. https://github.com/managarm/managarm

Neat idea. There is some research done on fully async OSes like https://github.com/managarm/managarm

If you haven't already, I'd hang out with the Managarm crew. Prety friendly, and what they're doing with C++ and async is very cool!

But well, maybe you should look at Managarm.

You can find more information on the project on our github page here. It is mostly a hobby project, so me and the other developers like to work on it in our free time.

Not hosted on rust-osdev but the Managarm project (an OS that focuses on async and that is primarily written in C++ so far) recently gained a rustc port and ports of some basic utilities written in Rust (ripgrep, exa). Support for Rust drivers is in the works (but still requires adding support for some libraries first that wrap the low-level system call interface).

If you have never seen an async OS, then you must’ve missed Managarm, a fully asynchronous operating system written in c++20. It’s a cool thing to check out, runs on x86_64 (a port to a raspberry pi4 is in progress) and has an extensive userland with various Linux applications running on a custom written libc. In case you’re curious, the repo can be found here: https://github.com/managarm/managarm

Not to be confused with Vale[0].

[0] https://vale.dev/

The article says they created a deterministic hypervisor that runs all pseudorandom behavior from a starting seed to enable perfect re-playability.

But that's all we know so far. I'm assuming there'll be some sort of fuzz testing, and static analysis or some defining actions that your software can perform.

Honestly it sounds a lot like it has a lot of crossover with what the Vale language is trying to solve: https://vale.dev/, but focused on trying to get existing software to that state instead of creating a new language to make new software already be at that state by default.

Why go through all the trouble when you can do this: https://www.hylo-lang.org/ and not spend a second thinking of lifetimes? No, copies will not be issued unless necessary.

Or why not keep exploring this idea as well? More research-oriented than the first one right now, though, so take it with a grain of salt: https://vale.dev/

Another relevant language might be Vale (https://vale.dev), which is aiming for "perfect replayability": https://verdagon.dev/blog/perfect-replayability-prototyped

Interesting. Very low level though and C(++) centric. She there any thoughts on combining the hardware and OS features with rust or https://vale.dev ?

Use a runtime memory management solution that's cheaper than garbage collection (see Vale)

This seems like a tool I'll be using, and this is an almost meaningless criticism, but why the name?

There's already the Vale programming language (https://vale.dev/), but moreover, I don't get the meaning of "vale". You could call it something like Englint which actually hints its purpose.