3 ms·
For context, the author (estebank) is the current force behind the Rust compiler's excellent error messages. To reiterate the lede, so it doesn't get buried: "
by kibwen 3y ago
For context, the author (estebank) is the current force behind the Rust compiler's excellent error messages.
To reiterate the lede, so it doesn't get buried: "I’m convinced that rustc should never have the capability to make network connections. [...] When it comes to Rust, users’ machines are (and should be) entirely under the users’ control."
(And I don't believe this post is a response or a rebuttal to anything in particular, other than possibly being in the news because of Go. Telemetry was considered for the Rust compiler pre-1.0 and rejected for privacy reasons, and AFAIK has never seriously been pursued since.)
- SkyMarshal 3y agoTbf he didn't bury the lede, it's right in the second paragraph: > I believe that no compiler needs to call home. But I also believe that we have a viable alternative if we reject the `tele` part of telemetry. Local metrics that are never sent anywhere can still give us valuable insight about how the Rust compiler is behaving.