News for hackers. Stuff that matters.

disappoint

Re:Thoughts on Go vs. Rust vs. Zig on Friday December 05, 2025 @02:57AM (#46157838)
You are again making deceitful, false and wrong excuses on purpose. Do better.
Re:Thoughts on Go vs. Rust vs. Zig on Friday December 05, 2025 @02:56AM (#46157834)
You are making false and wrong excuses on purpose. Do better.
Re:Thoughts on Go vs. Rust vs. Zig on Friday December 05, 2025 @02:55AM (#46157820)
Yet it is not a nitpick. Do better.
Re:Thoughts on Go vs. Rust vs. Zig on Friday December 05, 2025 @02:52AM (#46157796)
Shold one compare Rust with C or Rust with C++? Modern C++ provides a lot of features that makes this topic easier, also when programs scale up in size, similar to Rust. Yet without requirements like no universal aliasing. And that despite all the issues of C++.

> Even if we accept the premise that unsafe Rust is harder than C (which frankly is ludicrous on the face of it)

It clearly is not ludicrous, but true, as you well know.

> we’re talking about a tiny fraction of the overall code of Rust programs in the wild.

Which is wrong, also because unsafe Rust can require way more validation of code than just the unsafe blocks themselves. Do you not know or understand the basics of unsafe Rust? If so, that counts both against you and even further against Rust. Know your language!

> With all due respect this may be the singular dumbest argument I’ve ever had the displeasure of participating in on Hacker News.

You are describing yourself, and you are the source of that, and your arguments regarding the blog posts of famous developers are severely lacking. You clearly have no shame, no honesty, nor any competence.

Re:Thoughts on Go vs. Rust vs. Zig on Friday December 05, 2025 @02:43AM (#46157750)
And it can easily be more than 5%, since some projects both have lots of large unsafe blocks, and also the presence of an unsafe block can require validation of much more than the block itself. It is terrible of you and overall if my understanding is far better than yours.

And even your argument taken at face value is poor, since if it is much harder, and it is some of the most critical code and already-hard code, like some complex algorithm, it could by itself be worse overall. And Rust specifically have developers use unsafe for some algorithm implementations, for flexibility and performance.

Re:Thoughts on Go vs. Rust vs. Zig on Thursday December 04, 2025 @11:01PM (#46156720)
Google's Android teams also categorize old C code as C++, and mix gotos into their modern C++ code.
Re:Thoughts on Go vs. Rust vs. Zig on Thursday December 04, 2025 @10:58PM (#46156711)
> This could happen in every language ever made. It has nothing to do with rust.

Except it does. This also has to do with culture. In Rust, I get the impression that one can set it up as roughly two communities.

The first does not consider safety, security and correctness to be the responsibility of the language, instead they consider it their own responsibility. They merely appreciate it when the language helps with all that, and take precautions when the language hinders that. They try to be honest with themselves.

The second community is careless, might make various unfounded claims and actions that sometimes border on cultish and gang mob behavior and beliefs, and can for instance spew unwrap() all over codebases even when not appropriate for that kind of project, or claim that a Rust project is memory safe even when unsafe Rust is used all over the place with lots of basic bugs and UB-inducing bugs in it.

The second community is surprisingly large, and is severely detrimental to security, safety and correctness.

Re:Thoughts on Go vs. Rust vs. Zig on Thursday December 04, 2025 @10:50PM (#46156675)
SAFETY comments do not magically make unsafe Rust correct nor safe. And Miri cannot catch everything, and is magnitudes slower than regular program running.

https://github.com/rust-lang/rust/commit/71f5cfb21f3fd2f1740...

https://materialize.com/blog/rust-concurrency-bug-unbounded-...

Re:Thoughts on Go vs. Rust vs. Zig on Thursday December 04, 2025 @10:44PM (#46156650)
Please explain the differences in typical aliasing rules between C and Rust. And please explain posts like

https://chadaustin.me/2024/10/intrusive-linked-list-in-rust/

https://news.ycombinator.com/item?id=41947921

https://lucumr.pocoo.org/2022/1/30/unsafe-rust/