←back to thread

The Tor Project is switching to Rust

(itsfoss.com)
348 points giuliomagnifico | 1 comments | 12 Dec 25 12:35 UTC | HN request time: 0.223s | source
Show context
anthk ◴[12 Dec 25 13:25 UTC] No.46243905[source]▶
Why not Go? It's more portable.
replies(7): >>46243939 #>>46243943 #>>46243983 #>>46244203 #>>46244559 #>>46262087 #>>46262252 #
lynndotpy ◴[12 Dec 25 13:36 UTC] No.46243983[source]▶
Don't Rust and Go build to mostly-statically-compiled binaries? (With the exception of a link to libc.) (This isn't a rhetorical question, this is something I don't know a lot about

I'd imagine the biggest cultural reason is that many Rust developers were C developers who had a reason to find something better, but still scoff at garbage collection, large runtimes, etc. They probably have a lot more Rust expertise in their circle.

Another technical reason is that they were trying to replace their C code with Rust in bits and pieces before they went with a full rewrite. I don't know about Go, but this is something ergonomically doable in Rust.

replies(2): >>46244359 #>>46244948 #
1. atq2119 ◴[12 Dec 25 14:18 UTC] No.46244359[source]▶
Plus, Rust has a more expressive type system.

I like loose type systems for some quick scripting, but I started to adopt Rust for many of my personal projects because I find it's so much easier to get back into a project after a year when there are good type system guard rails.