I have no problem with Rust strengths or goals, but it needs to start focusing more on showing those strengths and less on envying other programming languages achievements trying to deceive mostly politically näive tech people by implementing Rust trojan horses, making gradual takeovers of popular projects so Rust have a place in the pantheon of the technological status-quo, where it can say how it bravely replaced the dangerous languages out there and the world is a better place for it.

This org is effectivelly a "rewrite in Rust" but now in its institutional form, so a line between random comments on the internet and the materialization of this goal have being crossed.

If they were really serious about security and memory safety, other memory safe languages would be covered and projects to at least harden (and why not move forward) the insane amount C and C++ code out there would also get covered.

(Today there was a C ISO about this popping to make this happen)

Trying to rewrite and if they see a chance, make hostile takeover of the projects might backfire and kill the host, because there's no guarantee that the knowledge, which is the actual important part of a project, will pass over in the process.

The real secret of C and C++ its not the syntax, but the time to form champions and knowledge. Those key people form knowledge around certain topics and they are formed together to build things. The same thing is happening in Go , Rust and whatever else right now.

In the case of Android for instance, where a hard line was drawn in the floor, there's a chance this changes dynamics in a way that, while i believe less memory safety errors will happen, it might drain the project in the long run, because dealing with such a big project with more than one language its a daunting task in a schizophrenic codebase.
People will be forced to learn Rust or get more and more sidelined in the org. Some will byte, but others will jump. In this process a lot of shiny material might get lost, and there's no guarantee that they will be passed over to the new code.

In the case of Linux nothing will happen really, its just a drop in the ocean, and maybe a virtualization package appears here or there, and that's why Linus didn't even bothered that much, he only was worried about those modules not freezing the kernel.

But in he case of Curl, Daniel is quite aware of the real motives and the dangers around it, but maybe the next guy isn't.

This org have an agenda. No problem with the agenda, but be open more about it or change course (really using the money for security in general).

By being open it also needs to say it when collect money from donors, so that X that was to donate money to Curl anyway don't get deceived into funnel its money into this org with a secondary agenda that might even turn out badly for the open source project.

Its not about C or C++ here, its about all the gold that is out there in those languages sometimes gold that will be not replaced, because its more about the human factors, dynamics and chance than language petty peeves.

Yes i understand how important memory safety is, and i want more of it and i like that Rust found a way to back it into the language and forced others to think more about it..

But lets not destroy the Sistine Chappel's out there because of ego, specialists thinking in unidimensionals aspect unaware of the other damages in the long run, and blind and/or young cultist followers that are just surfing in a feel good hype of belonging to something.

Just try to create your "Sagrada Familia" in Rust. The raison d'autre that you've cited will guarantee that there will be not very great things in Rust given the small industrial-era mentality. While by attracting builders and original thinkers it will..