logoalt Hacker News

raincoletoday at 7:16 AM4 repliesview on HN

I don't get it. Are we reading the same article? This article is so generic that it reads like vacuous truth to me. But I don't see their bitterness towards Rust (or anything, really. It's just vacuous.) from it. Is this person a famous anti-rust'er or something?


Replies

darkwatertoday at 7:32 AM

But it links to this post

https://joshlf.com/posts/memory-safety-life-and-death/

Under a "it doesn't matter it's memory-safe if..."

show 1 reply
Ygg2today at 12:43 PM

I don't get how you dont't get. It links about memory safety (with a link towards an extremely biased article in Rust's favor) and a link to design to correctness (that leads to Zig project).

There is a lot to dislike about this paragraph:

      It doesn’t matter that the language you use is memory-safe, if you didn’t design for correctness or have no process that will eventually lead you to fixing all bugs.
 
Hang on. If I want to prevent all bugs, shouldn't memory safe make your correctness much easier to achieve? And what is this about fixing all bugs? You mean proofs? The stuff that Zig doesn't aim to do?

And no, asserts don't fix all bugs, they just guarantee some of your invariants are held at best, used in test at worst.

show 1 reply
bigyabaitoday at 7:24 AM

> It doesn’t matter that the language you use is memory-safe

> nobody can trick me into mistaking lesser stars for my true destination

The author seems to be in some level of denial around compile-time safety checks. They're right that runtime safety errors are an issue, but it feels wrong to discount compile time checkers when it can save a lot of yak shaving.

show 1 reply
zuzululutoday at 7:47 AM

It's so bland and generic its bizarre like somebody is botting it. Weird that all the comments calling this out are getting flagged or downvoted.

show 3 replies