4 ms·
Static typing is a big one, but I've been so steeped in Python that I don't appreciate it as much as maybe I should. The big thing for me is that most Rust pro
by lynndotpy 1y ago
Static typing is a big one, but I've been so steeped in Python that I don't appreciate it as much as maybe I should.
The big thing for me is that most Rust projects are statically(ish) compiled (like go) and only need a `cargo build`. No venvs or pip commands or node/npm/nvm or make, etc.
- mdaniel 1y agoAlso, the Zen of Python is supposed to be one obvious way to do something but ddg "python dependency manager" and have a good laugh. That actually becomes triple lol for when uv steps in and says "uh, your pip requirements.txt is unsatisifyable, what are you even?!" And let me just say what an absolutely stellar job the rustc authors have done with the error messages. Just out of this world thoughtful. I have not yet gotten on board with their compile time vs safety and insight tradeoff, but I can see why they chose those two axes
- johnisgood 1y agoYeah, and static typing is not limited to Rust, and there are many other programming languages that do not have any of that venvs / pip nonsense.
- lynndotpy 1y agoWhat languages? I'm asking this earnestly, because there are dozens of languages I can name but I have not used. Every language I've used (except maybe Julia) asks you also to install and use something extra, like "meson" or "ninja" or "maven" or "cmake", for its build phase.
- johnisgood 1y agoYou want languages that can be compiled similarly to "cargo build"? Well, Go is one of them. Many C projects are just one "make" command away. OCaml has "dune build". Odin has "odin build", too. There are a lot of other languages I am missing here though.
- lynndotpy 1y agoOh yeah, right about Go. Odin and OCaml are languages I don't use but have heard their names. I'm not saying Rust has exclusivity here, I'm only explaining why I like to know a project was written in Rust.
- johnisgood 1y agoOkay, fair enough. :)