Until Rust gets the compilation story sorted out, what you save on the computer center gets spent in developer workstations.
Do you mean compile time?
> what you save on the computer center gets spent in developer workstations.
um, that cat is already out of the bag. unless you work on mobile or web frontend most backends are big, ugly, have a lot of dependencies, running them needs ALL the RAM anyway :)
C++ is slow as well.
True, except the tiny detail that the usage of binary libraries is common in C++ culture.
Building from scratch Gentoo style not so much.
I seldom compile third party dependencies.
You don't recompile those every time.
Indeed, only every time I checkout something from github, update cargo dependencies or switch worspace.
I would not use Gentoo if I had to compile the world to, say, update PHP.
Most large C++ codebases that have been running in production over decades are unfortunately a Frankenstein's monster written in a mix of old style C with classes C++ code full of malloc and free footguns, heavily OOP driven prefer-inheritance over composition era code full of virtual destructor footguns, and the modern nicer RAII std::unique/shared_ptr memory management based C++ code. And a lot of template and macro magic thrown in across each of those eras.
So you can get really productive in modern C++ pretty quickly and it can be an enjoyable experience. But to maintain a large old C++ codebase you are going to have to grok a lot of stuff. So much that I really can't find too many people who can hold it all in their head. I certainly can't.
Finally, am not sure if there was a hint of derision about Rust being primarily used for web services but I think it's a great thing if the next generation of web services will be developed in something as efficient as Rust rather than more resource hungry counterparts like Python or JS. Good for the balance sheet. Good for the environment. Good for the web devs who get expressive easy to understand code with a lot of guard rails built in.