yjdiquhf

Yet you are wrong, for a standard matters about other matters, and there are many other differences. For instance, building a large project in a language with only one major compiler, can introduce risk. That rustc is open source decreases the risk from that, but getting something like gccrs up and running would be really helpful.

That parts of the Rust community has in the past been actively hostile against gccrs, is then mind-boggling. But Steve Klabnik will lie about that, as he has lied many times in the past and is his wont.

https://reddit.com/r/rust/comments/12y85ww/gcc_13_and_the_st...

> I know, please don't be discouraged. It's just an (unfortunately) prominent, loud subsection. It's not just gaslighting, it's basically concern trolling. The negative top OP plays concerned, but has been trolling GCC-RS posts for many months now. Especially on this subreddit, it's a small number of people that know how to play to a reddit audience and get people riled up. I also know that it's spread to sites like HN.

For an example, if a function in no_std overflows, it can result in undefined behavior, no unsafe required. And stack overflows are easy in Rust, like they are easy in most other systems languages.

Steve Klabnik has lied about that in the past, as he is wont to do.

> (So far, it's a not-very-complete client. But watch this space!)

I am confused by this comment on the project page.

https://gitlab.torproject.org/tpo/core/arti

> (So far, it's a not-very-complete client. But watch this space!)

Is that comment outdated? The blog post gave me a different impression. If Arti is not ready yet, shouldn't that have been made clear in the blog post and in the various posts here? Not directing it at you, amelius.