| ▲ | randypewick 3 days ago |
| Damn this person's obviously is so bitter towards Rust... I wonder why he's so obsessed with it? I mean, if they really care about software correctness, I wonder why take a very discutibile position and say that "safety doesn't matter if you don't use the correct process". Yeah, I mean, having some guardrails is better than none, right? If they really cared about correctness, they would really strive to put all the possible guardrails in place, wouldn't they? Maybe they are bitter because their fav language is not as popular as the other? But there are so many languages, I wonder why picking on Rust specifically. |
|
| ▲ | raincole an hour ago | parent | next [-] |
| 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? |
| |
| ▲ | darkwater an hour ago | parent | next [-] | | 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..." | | |
| ▲ | jiggawatts 8 minutes ago | parent [-] | | You may be misinterpreting the intended meaning. It's like saying it doesn't matter if surgery is done another antiseptic conditions if the patient isn't also given a course of antibiotics during recovery. It's not an argument against safe practices, it's an argument for amending one kind of safety with others. |
| |
| ▲ | zuzululu 33 minutes ago | parent | prev | next [-] | | 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. | | |
| ▲ | raincole 26 minutes ago | parent | next [-] | | What 'all the comments'? There aren't many comments in this thread. You mean this: https://news.ycombinator.com/item?id=48432736 ? I flagged it too. I think the flag is quite justified. | | |
| ▲ | zuzululu 23 minutes ago | parent [-] | | oh I don't particularly care I'm just asking what is it about this article that is so worthy of being front page? I'm literally just calling out the content. I'm sorry for complaining. |
| |
| ▲ | gghh 12 minutes ago | parent | prev [-] | | It's bland and generic because it's a manifesto. Author (and HN submitter) is Loris Cro, aka @kristoff_it, VP of Community at Zig Software Foundation. In his role, devising as set of general guidelines to use as compass when things (inevitably! and often!) get very very muddy and Right v. Wrong is hard to tell apart -- both objectively, and also from the point of view of being a community leader with ton of vested interest -- is essentially one half of his job. Other half is abide to said guidelines. So @kristoff_it last week sat down, came up with three simple rules short enough he can print on a business card (or hang on his office wall or whatever), and posted them here to test if they make sense to the wider community. TLDR: yes can seem bland / generic but within context it makes sense to me author needed to distill his ethics in a nutshell. | | |
| |
| ▲ | bigyabai an hour ago | parent | prev [-] | | > 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. |
|
|
| ▲ | mobelkh 2 hours ago | parent | prev | next [-] |
| the piece didn't really seem very targeted at Rust as much as it's targeted at projects claiming to be secure just because they're written in Rust |
|
| ▲ | ares623 2 hours ago | parent | prev | next [-] |
| from his about page: "I'm VP of Community at the Zig Software Foundation" EDIT: doesn't really answer your question. Just reminds me of a good ol' flamewar. |
|
| ▲ | worik 2 hours ago | parent | prev [-] |
| > Damn this person's obviously is so bitter towards Rust What makes you think that? > I wonder why picking on Rust specifically. I did not see that. What did I miss? |