Mozilla's wiki [1] says Firefox has shipped more than 20 components implemented in Rust and has several more currently in progress. That sounds like tangible results.
The first component they implemented in Rust, I think, was the MP4 parser, in order to avoid exactly the kinds of vulnerabilities this article is about, which tend to occur in parsing code.
Servo was a major start to the Rust ecosystem (+ major help on Rust's path to a final design for 1.0) and also produced webrender and a few other pretty important libraries. Those are absolutely tangible results.
Pretty solid motivation for anyone who tries to tackle the browser market (a task I envy noone for) to go with a language like Rust. Inherent advantages + the incumbents can't get it to work internally.
I don't know there's a "browser market". As it is, I think the existing code bases are better served by gradually employing C/C++ verification and invariant checking tools. And not make the web any more complicated than it already is without a need (other than to maintain a browser cartel, that is).
Bad news, barely anyone is even thinking about it. There are one or two players that are trying to build a new browser from scratch, but they are far from mainstream and nobody knows how long these efforts will exist.
Completely untrue. Servo was from the start a research project, but even then, big components like webrender and stylo are now parts of Firefox, and there's a whole list more here: https://wiki.mozilla.org/Oxidation
What is completely untrue? When the Rust team was let go in 2020, only a very minor part of Servo (Stylo) delivered and became part of FF according to [1]. Yet the Rust core team, already notorious for lone language decisions, engaged in what amounted to an epic risk of a publicity catastrophe for Mozilla. And even in their post mortem in [1], they care more about progressing Rust than about their employer or the (much more important) work they were paid for.
And frankly I am upset by the way you characterize my post there. First of all, as I said, it was in a personal capacity, not a statement from the team. Second, as I was not employed by Mozilla at the time, of course I care more about Rust than I do Mozilla. However, that does not mean that I did not care for those who were let go, we were all very upset at how unfortunate the situation was. And the broader community stepped up and hired everyone, as far as I know.
And also language like "already notorious for lone language decisions," that is how both the Rust project and Mozilla wanted it! They actively did not control language decisions, even when Rust was small enough that the only folks who worked on it were at Mozilla. Nobody wanted Rust to be a single vendor technology, because of the exact risk of the situation that came to pass. Imagine if Rust were 100% Mozilla at that time, and they abandoned it. Instead of it being a bump in Rust's development, it would have been a catastrophe.
And, your original post: "the entire fsking Rust team." Again, Mozilla employed a very small number of people that made up the overall team. Yes, they were critical people, who did a lot of important work, but "fired the entire team" is straightforwardly inaccurate.
