There isn't a lot of good software written in Rust, open source or not. It's a lot of small and half-finished stuff here and there. The actual software out there is the ultimate, unforgiving, unfraudable review of a language, not what people say.
Developers seem to like Rust (or at least pay lip service). It's understandable. We are all suckers for a golden hammer. Rust promises no data races, no dangling pointers, high performance, and best of all it can run on numerous targets, making it a contender for The Last Language you have to know.
But you don't judge a restaurant's performance by the holiness of the chef's choice of tools in the eyes of other chefs. What is the most profitable piece of Rust software or the piece of Rust software that the most people depend on? If it wants to be taken seriously at the systems programming table, then we should see the Unix coreutils written in Rust (with all the command line flags working exactly the same way). Come on, replace GNU. You say you can do it faster and safer than everyone else. Let's see it.
Interesting. I thought that only find in project (ctrl shift f) was using ripgrep, but I kind of thought that find in current file (ctrl f) was done differently.
> we should see the Unix coreutils written in Rust (with all the command line flags working exactly the same way)
While I'm not convinced that implementing an identical API to coreutils is necessary to be "taken seriously" as a systems programming language, there's a fairly far along implemention that already exists:
> There isn't a lot of good software written in Rust, open source or not. It's a lot of small and half-finished stuff here and there.
Perhaps you and I have very different definitions of "a lot" or of "good", because I don't agree with this at all. There are plenty of high profile Rust projects with excellent production track records. Linkerd, TiKV, and Firecracker (originally crosvm) come to mind immediately, and of course Servo. Facebook also selected it for Libra, Google for Fuchsia.
Literally all of the things you mentioned (except linkerd which is mostly Go) are half-finished incubator projects. Rust has been around for over 10 years. Come on.
> Today, Lambda processes trillions of executions for hundreds of thousands of active customers every month. Last year we extended the benefits of serverless to containers with the launch of AWS Fargate, which now runs tens of millions of containers for AWS customers every week.
> Battle-Tested – Firecracker has been battled-tested and is already powering multiple high-volume AWS services including AWS Lambda and AWS Fargate.
That doesn't sound like a half-finished incubator project.
Linkerd consists of a "control plane" and a "data plane." You linked the the control plane, written in Go. You want the data plane, here: https://github.com/linkerd/linkerd2-proxy
Using language age as a definition of success isn't really being fair. Plenty of very successful languages took a long time to gain traction. For instance, Python was in a very similar position to Rust for almost 15 years before it finally started to shoot up into what it is today. In 2000 you were considered eccentric if you chose to use Python for anything but the most dirty scripts, but now it's being used for complex production systems.
I'm not blind. I can see that Rust has its major downsides, and the zealotry you see is on HN and elsewhere is downright annoying. But dismissing it based on age is being disingenuous. There was another list of projects elsewhere in this comment thread which listed a number of things being used in production that can't be considered half-finished by any measure.
Just my two cents: there are lots of Rust zealots in HN right now. Rust is at the top of its hype cycle rn, so it's a bit difficult to have balanced discussions even here. You're completely right with that Rust isn't one of the main language that drives the industry yet, but everyone will jump on you with tons of partial examples, and will claim it's already flying. Sigh.
Developers seem to like Rust (or at least pay lip service). It's understandable. We are all suckers for a golden hammer. Rust promises no data races, no dangling pointers, high performance, and best of all it can run on numerous targets, making it a contender for The Last Language you have to know.
But you don't judge a restaurant's performance by the holiness of the chef's choice of tools in the eyes of other chefs. What is the most profitable piece of Rust software or the piece of Rust software that the most people depend on? If it wants to be taken seriously at the systems programming table, then we should see the Unix coreutils written in Rust (with all the command line flags working exactly the same way). Come on, replace GNU. You say you can do it faster and safer than everyone else. Let's see it.