OpenVMM – A New VMM for Windows and Linux, Written in Rust

For real, I find it so odd to tack on "written in Rust" to every new project that's announced that uses Rust. (As someone who uses Rust in their day job)

As someone who does no programming at all, I can say that it kinda works.

It makes me think "Ok they have made a VMM again, but this time in that somehow safer programming language Rust. They probably know what they're doing so it will be just as good as the old one, only safer!".

I know enough to know that this is not necessarily true, but when I see these posts I always hope that it's true (and rely on people with the proper knowledge and experience to verify if it is or isn't).

Then I go to the comments and there is often a discussion about how a rewrite will probably be less secure because it will introduce new bugs. But then maybe those will be fixed and eventually it will just be a more secure version.

I consider a language mature, when it's developers stop feeling the need to list "written in X" in the features section of the repository/main page.

because languages matter more than people like to admit

yes you can write OOP in C , but please don't

and you can write fp code in Java .. this one I am not so sure about, but I would say its still better to just use scala or clojure if you must JVM, and use just use ocaml and drop the no-tail-call-optimization-jvm

the point is .. languages matter

That'd be a poor criteria. C++ is now an immature language:

Show HN: Comprehensive inter-process communication (IPC) toolkit in modern C++ (2024) https://news.ycombinator.com/item?id=40028118

You're right. It does smack a little bit of insecurity (phycological, not in the CS sense). But, "blah blah blah `written by AI`" transmits a different signal than "blah blah blah `written in Rust`", at least for now.

"Written in Rust" to me implied that they're willing to go with a modern tech stack.

When I see that a project is written in Rust I assume that beyond the language, their other technology/library/framework choices also tend torwards what is modern and unstable, rather than what is conventional and solid.

That information is relevant to shaping one's view of a project. I think it makes sense to mention that you're using a modern stack.

(Though Rust is already close to moving into the conventional/solid category.)

Traditionally this would have been written in something like C, which, while conventional, is hardly solid in security-sensitive contexts like this one.

I also tend to think “will lack long term support”, as I’ve seen many Rust projects where the OG devs move on to other projects. It’s fine to do that of course, but when I see “X but written in Rust” I read it as “I made this as an exercise” and not “I am making a full attempt to replace this other project”.

Why is there a conflation between "modern" and "unstable", and "conventional" and "solid"? I've seen plenty of conventional things that are not solid, and plenty of modern things that were far from unstable. Or maybe I have a different threshold for what modern is.

Beyond your parenthetical, what about Rust is unstable for you today? It would be interesting to me to hear that in order to see if the things that come to mind when hearing that are the same that you meant.

Considering the continual revisions in C++ of fundamental things like pointers and strings, arguably this is not incorrect…

That's my read too. The "Written in X" suffix to project announcements makes them sound like stunts done for attention or clout, regardless of the language used. It reads like a headline "Man travels across America, with a unicycle."

I sort of see "written in Rust" as a feature. I guess they could say "memory safe implementation" but I suspect they'd also say "written in Ada" if it was in fact written in Ada as an example of another safe language.

First of all, there's no spec, no stable ABI, etc etc etc. And the language is constantly adding new features and complexities.

In practical terms and in this case it probably doesn't matter, but that is what people are talking about when they say it's both modern and unstable. It's not entirely unreasonable.

Note that "unstable" doesn't necessarily mean "broken". It just means that the ecosystem is likely to have changed massively looking back at code written today from some theoretical vantage point 5 years in the future.