3 ms·

Oh please. Preaching about safety in a globally inter-connected world devoid of privacy. Newsflash, it's not a language's job to make software safe. It's job i

Oh please. Preaching about safety in a globally inter-connected world devoid of privacy. Newsflash, it's not a language's job to make software safe. It's job is to make programmer's job as simple as possible: ie. writing new software. If your language fails to do that, people will not use it, plain and simple. How else could you explain the popularity of languages such as Python and Go?

adgjlsfhk1 5y ago
You'll notice that both of those languages also give you safety by default. It's pretty much only C and C++ that still make programmers write artisanal memory leaks. I didn't really understand Rust, until I saw a Cppcon talk about how to use STD.unique_ptr correctly, and I realized that the rust borrow checker is just that talk implemented in a compiler.
hiptobecubic 5y ago
How can you explain the popularity of big macs and coca-cola if the purpose of food is to help people build healthy bodies? Maybe your criteria isn't universal?
- wheelerof4te 5y ago
  We are talking about software here, don't change the subject please. My language preference won't make me unhealthy.
phicoh 5y ago
If your project can be written in Python or Go, then yes, do that. I don't think Rust is trying to compete with Python or Go. However, if the project needs a low-level language. Then skip C and C++ and use Rust. Almost from the start, high level languages have been about safety. In assembly, memory is untyped. That leads to way too many bugs. So languages evolved to get more eleborate type systems. Compare for example K&R C with lacked function prototypes with current C that does have them. That saved huge numbers of bugs. Traditionally, garbage collectors had to be used to maintain memory safety. However, that conflicts with many of the uses of C. So Rust had to come up with something that is both safe and compatible with C.
adwn 5y ago
> Preaching about safety in a globally inter-connected world devoid of privacy. What kind of logic is that? "Because Google sells your data, I don't have to worry about memory safety bugs in my code." Come on.

adgjlsfhk1 5y ago

You'll notice that both of those languages also give you safety by default. It's pretty much only C and C++ that still make programmers write artisanal memory leaks. I didn't really understand Rust, until I saw a Cppcon talk about how to use STD.unique_ptr correctly, and I realized that the rust borrow checker is just that talk implemented in a compiler.

hiptobecubic 5y ago

How can you explain the popularity of big macs and coca-cola if the purpose of food is to help people build healthy bodies? Maybe your criteria isn't universal?

wheelerof4te 5y ago
We are talking about software here, don't change the subject please. My language preference won't make me unhealthy.

phicoh 5y ago

If your project can be written in Python or Go, then yes, do that. I don't think Rust is trying to compete with Python or Go. However, if the project needs a low-level language. Then skip C and C++ and use Rust. Almost from the start, high level languages have been about safety. In assembly, memory is untyped. That leads to way too many bugs. So languages evolved to get more eleborate type systems. Compare for example K&R C with lacked function prototypes with current C that does have them. That saved huge numbers of bugs. Traditionally, garbage collectors had to be used to maintain memory safety. However, that conflicts with many of the uses of C. So Rust had to come up with something that is both safe and compatible with C.

adwn 5y ago

> Preaching about safety in a globally inter-connected world devoid of privacy. What kind of logic is that? "Because Google sells your data, I don't have to worry about memory safety bugs in my code." Come on.