←back to thread

171 points g0xA52A2A | 2 comments | | HN request time: 0.001s | source
Show context
ericyd ◴[] No.41869293[source]
Thank God this VMM is written in Rust, otherwise I would be very skeptical. I don't care about features or purpose or technical advantages, give me Rust or give me death.
replies(4): >>41869380 #>>41869386 #>>41871253 #>>41873298 #
mcflubbins ◴[] No.41869386[source]
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)
replies(6): >>41869445 #>>41869678 #>>41869752 #>>41869857 #>>41870126 #>>41874582 #
aniviacat ◴[] No.41870126[source]
"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.)

replies(3): >>41870513 #>>41870616 #>>41870846 #
1. estebank ◴[] No.41870846[source]
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.

replies(1): >>41880891 #
2. zifpanachr23 ◴[] No.41880891[source]
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.