1.0 on a web framework means the public API is a contract. Breaking it requires a major version. That is the news. The req/sec chart is not.
Rust on the web is still a hire-and-train problem. The framework does not change that. It does change whether you can upgrade in six months without rewriting extractors.
If you are choosing it for a JSON API with a small team that already writes Rust, 1.0 is the green light to stop pinning git SHAs. If you are choosing it to win a benchmark against Node, you are solving a problem you do not have.
Read the migration notes from 0.x. Anything that still says “subject to change” in the extractors is where you will spend the weekend.