Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    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?

    Comment


    • #32
      Originally posted by Delta_44 View Post
      I usually don't write something, I'm more of a daily lurker here, but now I'm pretty pissed.
      I'll explain why.

      When I first discovered this forum I thought it was beautiful that I'd finally found competent people to learn new things with comments, after reading Michael's articles.
      I still think this is a beautiful place to learn, but let me get something straight.

      This whole bullshit surrounding "Rust VS C (and everything else)" and "Nvidia VS Amd" is pissing me off badly.

      I come here to learn something useful, not to read pointless bullshit about "Oh RusT iS BaD!111!!"
      I DON'T GIVE A SHIT ABOUT WARS, neither the remaining sane part of this forum.

      We have AVIS/BIRDIE spamming bullshit about "how Nvidia isn't evil" (wrong) and "AMD sucks like Nvidia" (objectivly wrong, AMD could still be a "bad company" but it's doing more than Nvidia, thus the statement is wrong), we have other people shitting on Rust everytime something gets rewritten or a new "rust drama" happens.

      I'm fed up with this.

      I come here to learn your insight and I always read how a language that I personally like more than others (rust) is getting shat on, NOT FOR GOOD REASONS but with pointless "back in my day" stuff and "C is older thus is more widespread and it's as secure as Rust".

      Sure, in rust I can build something and forget about memory management, in C you have to think about it.
      I know almost nothing about C or rust, but I know enough to know that rust has a lot of advantages and interesting stuff.

      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.
      No having fun allowed?

      Comment


      • #33
        Originally posted by ssokolow View Post

        *nod* Efforts like that to get the priority bumped on fixing compiler bugs by making them famous happen from time to time.

        The important things to keep in mind are:
        1. These sorts of things tend to be really esoteric edge-cases that are almost impossible to write unless you're actively trying to do this.
        2. rustc is not and will never be intended to serve as a security boundary. Priorities on fixing these sorts of things are set based on a target user base of programmers who are writing non-malicious projects or auditing submission to them.
        3. There are a ton of these sorts of bugs in any compiler.
        For rustc, you can take a look at the I-unsound tag on the bug tracker to see what I'm talking about. I know LLVM and GCC both have plenty of similar bugs, but I'm not familiar enough with how they use their bug trackers to give you a comparable link.
        Well, this one is not really multiple compiler bugs. They're just having some fun by building upon a very well-known issue (https://github.com/rust-lang/rust/issues/25860, see also https://crates.io/crates/fake-static).

        Comment


        • #34
          Originally posted by cl333r View Post
          You're VERY naive, you had a wrong impression about the phorum from the start, you don't know people, you're only learning what actual people think (except those who kinda represent certain companies so they know they must behave here). Here's some Linux codenames for you to realize how "grown-up" the Linux community is:

          2.6.23 - “Pink Farting Weasel”
          2.6.25 — “Funky Weasel is Jiggy wit it”
          2.6.28 — “Erotic Pickled Herring”
          2.6.35 — “Sheep on meth”
          4.0 — “Hurr durr I'ma sheep”
          4.7-rc1 — “Psychotic Stoned Sheep”
          Let grown-ups have their fun too, there's really nothing wrong with choosing a couple absurd codenames. Way better than "when they rewrite something, they can't come up with their own things, when they build new stuff, it's not production-tested, and it's a religion anyways" (Rust/C, systemd/sysvinit, Wayland/X11) or personal attacks ("the communists/trannies/shamans are ruining everything").

          Comment


          • #35
            Originally posted by archkde View Post

            Well, this one is not really multiple compiler bugs. They're just having some fun by building upon a very well-known issue (https://github.com/rust-lang/rust/issues/25860, see also https://crates.io/crates/fake-static).
            Hmm. I guess I messed up my phrasing. I didn't intend to say it was multiple bugs but, rather, that there have been multiple crates like this over the years, each of which would be trying to draw attention to only one bug, and there exist multiple soundness bugs.

            I'm not even sure if any of them surfaced a different bug or if they were all surfacing that same one and, since I was focused on bookmarking stuff I felt was useful all I remember is that they got mentioned in /r/rust/ some time between 2015 and now.

            Comment


            • #36
              Originally posted by varikonniemi View Post
              Would be nice if phoronix would tell how many LOC of C this 3k of rust code is replacing.
              I don't think that's the task of phoronix. They published this news from elsewhere, it's not originating from phoronix nor are they taking sides in this endless Rust vs C discussions that are very amusing to read (to me). Especially if people take things personally (not you obviously).

              Comment


              • #37
                Originally posted by cl333r View Post
                You're VERY naive, you had a wrong impression about the phorum from the start, you don't know people, you're only learning what actual people think (except those who kinda represent certain companies so they know they must behave here). Here's some Linux codenames for you to realize how "grown-up" the Linux community is:

                2.6.23 - “Pink Farting Weasel”
                2.6.25 — “Funky Weasel is Jiggy wit it”
                2.6.28 — “Erotic Pickled Herring”
                2.6.35 — “Sheep on meth”
                4.0 — “Hurr durr I'ma sheep”
                4.7-rc1 — “Psychotic Stoned Sheep”
                my favourite one is https://git.kernel.org/pub/scm/linux...61c2cb84ade622

                Comment


                • #38
                  Originally posted by milkylainen View Post
                  I'd rather waste my life writing something new instead of rewriting existing things.
                  Maybe that's just me.
                  Then you probably do not work in software development. Rewriting existing code is fundamental for maintaining software. While I am not familiar with the specifics, I am very confident that there were multiple iterations and parts that were rewritten which are now rewritten again.

                  Comment


                  • #39
                    I'll start using rust when a$$ley williams is dead and rust woke foundation is gone.
                    Last edited by Volta; 17 September 2024, 08:09 AM.

                    Comment


                    • #40
                      Originally posted by LtdJorge View Post

                      It's the classic Linux circlejerk, pluse the classic C circlejerk, compounded by the Phoronix trolls. The forum is full of them. Just take them as a joke and have a laugh, you'll be less pissed with this.
                      Anti Linux rust amoeba? You're the joke clown.

                      Comment

                      Working...
                      X