Rewriting in Rust is not a meme, it's a cycle.

Before Rust became viable, rewrites were done in Go.

From the archives:

- Rewriting a large production system in Go https://news.ycombinator.com/item?id=6234736 (2013)

- How We Moved Our API From Ruby to Go https://news.ycombinator.com/item?id=9693743 (2015)

- Matrix and Riot Confirmed as the Basis for France’s Secure Instant Messenger App https://news.ycombinator.com/item?id=16938545 (2018)

- Toward Vagrant 3.0 https://news.ycombinator.com/item?id=27476676 (2021)

- I’m porting the TypeScript type checker tsc to Go https://news.ycombinator.com/item?id=30074414 (2022)

Which is why old timers eventually learn to just deliver with boring technology.

> Which is why old timers eventually learn to just deliver with ~~boring~~ buggy technology.

There's a reason why folks take the time to rewrite things in Rust. No matter how good you are at C/C++ you will encounter bugs that you would not have if you had written it in Rust.

Assuming there is even a Rust library replacement to start with.

People keep forgetting C++ has 30 years of being deployed in production.

Rust is 2022 is like using C++ in 1990's in terms of ecosystem.

This is just plain false. C++ in the 1990s had nothing like serde for example.

Where are the production grade and pure rust tls library ? Key-value store ? Ldap client ? SSH client ?

Regardless, I'm surprised you haven't heard of rustls - https://github.com/rustls/rustls