@josias@theres.life
Go is not safe in any way that rust is.
@janriemer

@josias@theres.life @janriemer
Saying Go is safe is the same as saying C is safe, or Java is save,... Just plain wrong.

@musicmatze @josias @janriemer Go is much more safer than C, for example access out of bounds or dereferencing a null pointer is caught properly with a nice message instead of plain "Segmentation fault" or reading/writing to random data.

Aside: I don't really understand why everyone fights for safety so hard. Do you not trust yourself writing code? Yes, safety features that languages provide are very useful and catch mistakes but it's not really something that is a yes/no question.

@yyp
> Aside: I don't really understand why everyone fights for safety so hard. Do you not trust yourself writing code?

You might trust yourself and let's say you write 100% flawless code all the time, but here is the thing: it doesn't scale! Any reasonably sophisticated software is written in a *team* and so person A has different perspectives/experiences/assumptions than person B.

There is a reason why 70% of vulnerabilities in big software are memory-safety related.

@musicmatze @josias@theres.life

@janriemer @musicmatze @josias Are you trying to tell that Rust is The Programming Language™ and everything else is worthless?

The problem with big software having memory issues is that it's usually hard to track down where things are allocated and cleaned up. If you structure your code well, this won't even be a problem.

@yyp
> Are you trying to tell that Rust is The Programming Language™ and everything else is worthless?

Nope, I haven't said that with a single word. But interesting you interpret it that way. 😉

Yes, _you_ can structure your code well, but as I said, it's a team sport.

Oh, and have you ever tried to write multithreaded, concurrent applications?
It hard pretty is, Rust when not using $%&$§/&%%n​ot rè̑ͧ̌aͨl̘̝̙̃ͤ͂̾̆ ZA̡͊͠͝LGΌ ISͮ̂҉̯͈͕̹̘̱ TO͇̹̺ͅƝ̴ȳ̳ TH̘Ë͖́̉ ͠P̯͍̭O̚​N̐Y̡ H̸̡̪̯ͨ͊̽̅̾̎Ȩ̬̩̾͛ͪ̈́̀́͘ ̶̧̨̱̹̭̯ͧ̾ͬC̷̙̲̝͖ͭ̏ͥͮ͟Oͮ͏̮̪̝͍M̲̖͊̒ͪͩͬ̚̚͜Ȇ̴̟̟͙̞ͩ͌͝S̨̥̫͎̭ͯ̿̔̀ͅ

😉

@musicmatze @josias@theres.life

· · Web · 1 · 0 · 1

@janriemer @musicmatze @josias

> Nope, I haven't said that with a single word. But interesting you interpret it that way. 😉

You're trying to tell that writing good code doesn't scale, but with Rust it does because it's safe. From this I conclude that no language is scaleable except Rust.

> Oh, and have you ever tried to write multithreaded, concurrent applications?

No, because I don't think they are worth that much. An event loop or multiple processes work just as well.

@yyp
> From this I conclude that no language is scaleable except Rust.

I agree with this much more, because it is very different from saying "every other language is worthless".

> An event loop or multiple processes work just as well.

Yes, there are situations where this is enough. For me, though, I like to have options.

Thank you for the debate. It was interesting to hear your opinion on this.🙂

@musicmatze
(taking Josias out of the conversation)

Sign in to participate in the conversation
Mastodon for Tech Folks

mastodon.technology is shutting down by the end of 2022. Please migrate your data immediately. This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!