The part I’m more interested in has less to do with “Rust type safety etc” and more to do with dependency management. Most C libraries out there are managed with configure and Makefile, which feel like it’s 1976 and are generally a pain to work with. On the other hand cargo will make integrating Arti crates a breeze, and that’s what I’m really looking forward to, the easy interop.
Yes, that's another part of rust that I also find much better.
Another feature is that it seems easier then C/C++ to statically compile everything into a binary (like Golang does). It solves other kind of problems, too.
Let's hope to see a Manyverse that uses Tor soon!
That's cool. I wish Mozilla would replace everything non-js on Firefox with rust, too. ;-)
Admittedly #rust appeals to the most nitpicky, pedantic and obsessive maniacs, making them spend all their time reimplementing things in rust because rust, so I suppose without rust they’d be bothering everyone else again instead of melting their brains in absolutely un-asked-for needless labor.
Although it really seems like it, they do have a point. There are lot's of errors that the rust compiler catches at compile time that many other languages don't. It also get's you a lot more of the CPU. So, in general:
Rust programs tend to need fewer code-test-run cycles to have the same reasonable number of bugs as programs written in other programming languages;
Since rust doesn't use garbage collection, the resulting program is faster on the same CPU as other software and also more deterministic, good for real time programming or games, for instance;
Since rust programs don't use manual memory allocation either, the tend to have less related bugs, as compared to languages with manual memory allocation (see #1);
Now, rust is not for everyone or even everything. The borrow checker brings a lot of cognitive burden on the programmer.
#rust #programming #languages
Show whole feed