Rust has the advantage that when compiled to WASM it won't require a runtime library. So the prospect of Rust as a fast, low overhead, use anywhere language is tempting.
Since Rust is a relatively new language it's worth checking to see how it's maturing over time against small low risk projects exactly as the author has done.
Rust may not be a perfect fit right now but that may change. So it's very valid to test one's assumptions from time to time.
Or to put it another way, working in one of the languages you've mentioned wouldn't answer the question "how suitable is Rust for web server work right now?"
Nevertheless, WASM is not ideal for server work. It is intended for the frontend.
I'm not suggesting that you would use WASM for server work at all.
I'm suggesting that Rust would be interesting for WASM on the frontend because it doesn't depend on a runtime.
Given that you might want to use Rust for WASM you may also want to use it on the backend (that's without using WASM on the backend).
The assessment of Rust via small projects says nothing about the suitability or not of C or any other language.
It's just about the suitability of Rust right now and how it's changed from the last time you assessed it.
> The project is simple enough that I can't imagine being too limited by any language's ecosystem. And I've been itching to write something substansive [sic] in Rust...