Me too. It’s a hello world web service I wrote while reading a tutorial after work this afternoon.

Thanks for the laugh I needed that

By definition, no software goes down until its lifetime ends.

I would say the lifetime of a piece of software is different from the lifetime of the process running it.

Good for you!

Now, if your Rust code was a distributed system that handles spiky loads from ~330m users, and processes petabytes of data, then I'd consider your comparison relevant to Twitter.

But I'm going to assume it's not relevant.

P.S., I've written Java services that never went down, because they had a well defined domain and all potential errors were handled. But, I'm not about to compare that to all of frigging Twitter.

I wasn’t attempting to compare anything to Twitter…

The infra usually matters way more than the code. RAM or a disk will typically fail before the Linux kernel, and it's written in the boogeyman language.