Rust helped Servo. But Servo also helped Rust:
I encourage people to listen to Josh Matthews interview [0]. He talks about how, early on, Servo was a "guiding light for Rust".
0: https://podcasts.google.com/feed/aHR0cHM6Ly9ydXN0YWNlYW4tc3R...
I encourage people to listen to Josh Matthews interview [0]. He talks about how, early on, Servo was a "guiding light for Rust".
0: https://podcasts.google.com/feed/aHR0cHM6Ly9ydXN0YWNlYW4tc3R...
I think programming languages must be developed with their application. For Rust, it is Servo, Go is for Google, LUA is for scripting video games, Swift is for making iOS apps, and of course C is for UNIX.
However, I would not recommend it for anything that's concurrent, needs high performance and resides on the critical path (critical not in terms of performance but in terms of reliability) or is large / to be maintained by many teams. Just too easy to run into problems.
I don’t use Rust, but appreciate how it solves clear problems. I’m really impressed about the way key issues like packaging & distribution, documentation, and coding style/safety are addressed at the language level. I bet those features emerged from the need to address issues with the open source development model. Without servo, maybe those features don’t make it.
The outside world, though, appears to have embraced it.
C++ 295
Go 252
Java 235
Also the easiest way for a Googler to open source a hobby project is to open source it under Google's repos - otherwise you need copyright assignments and stuff that's harder to get approved. So it doesn't represent what most Googlers work on.
Google uses many languages beside Go, and I doubt Go is used much outside of cloud infrastructure stuff. E.g. Fuchsia/Android/Chrome add a lot of Rust code recently, but not Go. In Fuchsia, Rust already surpassed C++ in the amount of code. Google was always a heavy user of C++ and Java and it looks like their modern counterparts are Rust and Kotlin.