Debate: Go vs Rust (Toolchain Privacy Practices)
Debate: Go vs Rust (Toolchain Privacy Practices)
This post is not related other previously published posts. But I want to know your opinions.
This debate does not focus on "which technology is better" or "which has better support", rather it focuses on which of these two technologies seems more acceptable in terms of privacy policy and user information management (on his respective toolchain, compiler, etc).
You're viewing a single thread.
Both need a binary of themselfes compiled by some glowie at some point in time. Only if you build them from ground up or inspect the current compiler you can be sure. Otherwise stick to existing C compilers.
Otherwise stick to existing C compilers.
And what makes C not need a binary compiled by some glowie at some point in time?
The funny paradox lmao.
Rust can be bootstrapped with mrustc to my knowledge
That's true (also with other software that isn't for development). But this is not the only tool there. Just see crates.io and pkg.go.dev registries.
I think the only way to get "anonymously" some modules, libraries and frameworks is trough Tor.
I don't think that was the question. I think you are responding to a question like "what if the go/rust compiler has a backdoor", but the actual question was which are better from a privacy perspective, and what that means in this context is whether they mine the user's data (the developer using it), or if they upload statistics of the user's system or the compiled program at all.