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

[lowflyer]

Ah for fuck's sakes, I give up.

Apparently I failed to communicate my real intentions, I'm sorry for that but I'm not going to squeeze my brain out now, I'm having a shitty month and I don't have to deal with this too, sorry for that and for disturbing "the peace" with a badly written rant, I just wanted to voice my opinion but I failed, miserably.

Maybe in future interactions, you guys will be able to understand me better, and maybe you'll be able to see that I'm not a troll, jeez.

Dear Delta_44, you have my full sympathy. Life sucks from time to time. Some of us carry heavy burdens unbeknownst to all others in the forum.

I don't think you failed. Despite the "fallout" and contrary to your impression, your opinion was seen and well received. Your original post received 17 likes (seventeen !!). Which is quite notable.

[Delta_44]

Delta_44 , you're dishonest. In your first post you wrote this:



You addressed everybody in this forum. How can a "grow up folks" and "why don't you spam reddit with this crap" not be seen as an attack? You're nobody's father in here: expect backlash. And when our brother Weasel replied, you try to make him the attacker??? That's what trolls do.

I don't know how much life is left in your thinking license, but if I were you, I'd run to renew that thing immediately.

Ah for fuck's sakes, I give up.

Apparently I failed to communicate my real intentions, I'm sorry for that but I'm not going to squeeze my brain out now, I'm having a shitty month and I don't have to deal with this too, sorry for that and for disturbing "the peace" with a badly written rant, I just wanted to voice my opinion but I failed, miserably.

Maybe in future interactions, you guys will be able to understand me better, and maybe you'll be able to see that I'm not a troll, jeez.

[lowflyer]

My friend lowflyer If you'd bothered reading his comment, you'd find stuff like

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.

If this is not an "attacking tone", revoke my licence to think.

Delta_44 , you're dishonest. In your first post you wrote this:

When something "new" gets announced almost everyone disregard it and says "it's shit".

Maybe it's time to grow up folks.

By the way, why don't you guys spam reddit with this crap?
Keep a technical forum objective, not full of garbage.

This ain't facebook or X, this is a "technical forum" which should have even comments from professionals, not from trolls.

You addressed everybody in this forum. How can a "grow up folks" and "why don't you spam reddit with this crap" not be seen as an attack? You're nobody's father in here: expect backlash. And when our brother Weasel replied, you try to make him the attacker??? That's what trolls do.

I don't know how much life is left in your thinking license, but if I were you, I'd run to renew that thing immediately.

[Weasel]

I'm expected to be attacked by the one I'm attacking

It's a public forum, I couldn't care less about your expectations. I see your crappy post, I reply.

You attack people I share opinion with, I will attack back. Simple.

I'm not expecting anything by the way

You literally started this reply with an expectation. lmfao.

Hell I don't even care if you insult me or something, I just stated the fact that it was a plain attacking reply, while I just diplomatically posted a reply stating "I personally like rust but I don't insult other languages" and all I get is "cry me a river"?

That was stupid

Your entire first post was inciting drama and crying about it, that was what it was referring to.

[Delta_44]

Attacking someone and then not expecting to get attacked back.

What?
I'm expected to be attacked by the one I'm attacking, literally no one quoted you, I certainly didn't, and you're putting words in my mouth that I've never said.

I'm not expecting anything by the way, my complaint was born because when I open the comment section I expect to gather insight, rather than reading the first 5 comments and seeing useless bullshit such as "oh rust is shit" or similar stuff.

I love drama in a sense that I grab popcorns and laugh at the things that I read about, for example, AMD vs Nvidia, but I don't always enjoy reading such things.
Since I'm not special, and you're clearly more intelligent than me (basing on your "tone"), kindly explain why you thought in a one-dimensional way: "either you enjoy something or you don't, no middle-ground here"

BUT THEN ... you see the comments of our brother Weasel as "an attack".

My friend lowflyer If you'd bothered reading his comment, you'd find stuff like

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.

If this is not an "attacking tone", revoke my licence to think.
Hell I don't even care if you insult me or something, I just stated the fact that it was a plain attacking reply, while I just diplomatically posted a reply stating "I personally like rust but I don't insult other languages" and all I get is "cry me a river"?

That was stupid

[Weasel]

So, you enjoy the drama, you say? But you want less of it? And you bemoan that people only see the worst in everything?

BUT THEN ... you see the comments of our brother Weasel as "an attack".

Well, my son, you actually feed the trolls as much as anyone else in this forum.

Exactly.

[Weasel]

So, tell me... what provoked your attack against me?

Attacking someone and then not expecting to get attacked back. Literal snowflake behavior. As I said, you are not special.

I mentioned birdie's posts because they're such a meme in this forum

Oh really, where's the meme meter to measure it? Science works with measurements.

I never said that I'm special

You literally posted complaints about drama while doing the same shit in return. YOU don't get to have your way if you don't want others to, either.

I received 17 likes, you received 3.

1 in 2 million people has an IQ over 180.

"us" agrees with me, plus there was no reason to attack me.

There was because you (plural btw) are a far bigger meme than birdie.

[ssokolow]

ssokolow, in the first CVE record that we can see there, we read "thus causing a memory leak". Didn't they tell us that it was "memory safe"? 🤔

Rust doesn't count leaking memory as violating memory safety because, in a turing-complete, non-research language, it's so hard to ensure that memory isn't leaked that it would make the term "memory safe" useless in practice if you included "can't leak memory" in it. There was actually an incident when they realized the former and decided on the latter which was dubbed the "leakpocalypse". (This was back before Rust v1.0 froze the language syntax and standard library.)

For example, you see memory leaks all the time in GCed languages like JavaScript... people just generally don't think of them like that because it dilutes the term to also apply it to "someone accidentally left something holding a reference to something else but the programmer doesn't realize it, so the program can't make use of it". The only difference is that, if you look at the thing in a heap debugger, the leaked memory is technically still reachable, so the garbage collector isn't freeing it. Likewise, leaked memory in Rust is technically still reachable if you go through your malloc/free implementation's internal bookkeeping data structures.

Hell, Rust has leak methods on various smart pointers as well as on Vec and String which don't require unsafe to call. They're intended for when you want to initialize a static (i.e. something that'll live for the rest of the program's lifetime without needing an owner to keep it alive) without having to use a an actual C-style global static.

See also the Behaviour not considered unsafe page in the Rust Reference. Having been around and seen the relevant RFC discussions, I can say that all of those things are thing the Rust team would love to catch at compile time, but cannot reasonably do so. (eg. For integer overflow, they compromised with runtime checks in debug builds because they couldn't find an acceptably performant way to trap them in release builds on x86. IIRC, either the linked RFC 560 or another one on the topic ended with them shelving that as "We've spec'd the flexibility to add that later. We can only wait on CPU manufacturers to add hardware support".)

The agreed-upon definition of "memory safe" is more or less what you get with something like a Python List or a JavaScript Array. When given a reference to a data structure in Rust, you can't break out of its bounds and modify unrelated memory (eg. overwriting the return pointer on the stack) without using unsafe and its raw pointer manipulation routines. More specifically, there are two kinds of memory safety, and Rust satisfies both:

• Spatial memory safety: Code can't manipulate memory outside the range it was given access to. (Which includes things like feeding garbage data to functions like free() and corrupting the allocator's internal state.)
• Temporal memory safety: No reading unintialized memory or use-after-free allowed. (Or double-free, for that matter, since passing something to free() is "using it".)

Every correctness guarantee Rust gives you beyond that is a nice benefit of having an advanced type system... but it's not part of what counts as memory safety in practical, real-world, non-academic contexts. (In academic contexts, things like "Program died because it tried to allocate more memory than the system had available" are sometimes also counted as memory safety, apparently... but good luck trying to rule out "Simple text editor without chunked loading or some other large-file optimization crashed because you asked it to open a BluRay ISO" at compile time.)

[Nth_man]

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

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

ssokolow, in the first CVE record that we can see there, we read "thus causing a memory leak". Didn't they tell us that it was "memory safe"? 🤔

[lowflyer]

So, tell me... what provoked your attack against me?
I mentioned birdie's posts because they're such a meme in this forum that everyone knows that he's mostly rage baiting or something like that.

I never said that I'm special, you talk about "us" but all I see is "I".

I received 17 likes, you received 3.

"us" agrees with me, plus there was no reason to attack me.

So, you enjoy the drama, you say? But you want less of it? And you bemoan that people only see the worst in everything?

BUT THEN ... you see the comments of our brother Weasel as "an attack".

Well, my son, you actually feed the trolls as much as anyone else in this forum.