A Re-Implementation Of The EROFS File-System In Rust Has Started

[Volta]

Here's some Linux codenames for you to realize how "grown-up" the Linux community is:

We have a stupid one here. It's not about the codenames, but code and actions. Winblows fanboys can't stand their utter crap OS became a meme. Meanwhile rust joke foundation behaves like a little mentally ill kid. There's no way one can take this crap seriously. Everyone must hear about rust foundation woke members and their behavior. Nobody will want to deal with such clowns then.

[klh_io]

Everyone must hear about rust foundation woke members and their behavior.

Counter-argument: nobody cares and you lose all credibility by using the word "woke" in your argument

[LtdJorge]

We have a stupid one here. It's not about the codenames, but code and actions. Winblows fanboys can't stand their utter crap OS became a meme. Meanwhile rust joke foundation behaves like a little mentally ill kid. There's no way one can take this crap seriously. Everyone must hear about rust foundation woke members and their behavior. Nobody will want to deal with such clowns then.

Prime example of said trolls.

[Weasel]

I know the forum is full of them and yeah, I enjoy the drama... way more that I should actually.
The thing is: I want to discover new stuff, learn things, learn different point of views.

Instead you have birdie complaining about AMD and saying wrong shit like "nvidia's open-source DRIVER" (kill myself), you have random people (that nobody ever see them here, they just spawn like mold) saying the most useless things straight out of reddit, that doesn't explain their point of view and you're just left wondering: "what did he say?"

I'd take everything as a joke, if you'd have 90% less stuff like this.

Plus: the eternal systemd hate... just stop it.
I get that systemd is like that one program that suffers from feature-creep and works like windows vista, but if systemd is so widespread there must be a reason for it.
But well, people has to only see the worst in everything.

You're not special. You realize your posts are just as bullshit to us as you find the ones you explicitly targetted like birdie, right?

You like Rust? I don't. So cry me a river that I post as such.

I don't care about what you want, just like you don't care about what I want. Sounds like we're even.

And I will continue to do so, because you are not special, and you do not have special privileges. Rust is also not special and does not deserve special privileges just because YOU or a bunch of other circlejerks like it.

[Nth_man]

Speykious/cve-rs: Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀 (github.com)

CVEs (Common Vulnerabilities and Exposures) in Rust programs:

https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust/

[lowflyer]

Let me just throw my words in, I agree C is not a good language by modern standards, and that Rust is a better language in lots of ways (though not all).

But at the same time I do not think Rust is a good C replacement and that the Linux devs should've focused on a language more similar to C instead.
Sure it might no be as memory safe as Rust or whatever but what is the point of a new language that often needs complete software redesign for a rewrite from C? Wouldn't it be much better if we had a perhaps not as safe but much faster to port C code to language in the kernel instead allowing for much more rapid rewrites?

Well, that language already exists. It is called C++. Linus did a terrible disservice to the whole community with his rant against it. Over the years his sycophants made sure that every one was shunned that just mentioned C++.

[ssokolow]

CVEs (Common Vulnerabilities and Exposures) in Rust programs:
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust/

Bear in mind that, by the standards of languages like C, the Rust ecosystem is a bunch of hypochondriacs.

For example, CVE-2019-25007 in that list is "An issue was discovered in the streebog crate before 0.8.0 for Rust. The Streebog hash function can cause a panic." That description isn't saying "some inputs cause a security breach", it's saying "some inputs cause an ASSERT failure". It's literally a CVE because "it's possible to hold it wrong".

(I get the impression that CVEs like that aren't filed directly by Rust ecosystem people but, instead, some organization is replicating entries in the RUSTSEC database into the CVE database... RUSTSEC being used by tools like cargo-audit and cargo-deny with the intent to eventually get RUSTSEC warnings into regular Cargo dependency management commands in some capacity as NPM does.)

Another example would be CVE-2019-25009, which says "the HeaderMap:rain API can use a raw pointer, defeating soundness"... basically a vulnerability report for something that is a standard part of what C lets you do without any ceremony.

The difference is particularly pronounced in https://github.com/rust-fuzz/trophy-case with how tame the list looks compared to the results of fuzzing C and C++ programs.

RUSTSEC also contains entries which haven't been coped into CVEs like RUSTSEC-2024-0370: proc-macro-error is unmaintained.

[ssokolow]

Michael Poke, poke. Unapproved.

[MillionToOne]

Counter-argument: nobody cares and you lose all credibility by using the word "woke" in your argument

Clearly you cared enough to comment

[geerge]

I like C. I like rust. I like Linux. I like ice cream.