181–184 of 184 posts
Earlier quoted context omitted.
I find it funny and sad at the same time that an installer for a "safe" programming language teaches people to download a shell script from a website and run it. What a farce.
Read what the “safe” means. It is narrow. Memory safety.
Earlier quoted context omitted.
Go just feels a lot less productive to me than Rust. It feels very low level and boilerplate-intensive like C even though it has a garbage collector.
A team can learn and start using Golang in a week. That is in fact what is powering a lot of companies right now. Golang has even better memory safety guarantees than Rust and you don't really need to worry about memory management at all... Furthermore its compiled statically and more suitable for distribution and horizontal scaling. I am not sure how quickly a team can become productive in Rust but I am willing to b…
Earlier quoted context omitted.
I don't believe this is correct. I have not once seen a new method being added to stdlib that causes code to not compile. And ABI concerns are a non-issue since Rust is statically linked.
It is correct. For example, this code (admittedly a contrived example, just to illustrate the point) compiles in 1.82 but not in 1.83: trait OptionExt { fn get_or_insert_default(); } impl OptionExt for Option { fn get_or_insert_default() {} } fn main() { Option:: ::get_or_insert_default(); } The reason is that `get_or_insert_default` was added to the stdlib in 1.83, and takes a different number of arguments, so it cl…