Announcement

Collapse
No announcement yet.

Rust-Written Replacement To GNU Coreutils Progressing, Some Binaries Now Faster

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

  • Originally posted by Steffo View Post

    There is no single reason why C is faster. Everything which is possible in C, is possible in Rust. But the other way around is not true. In fact, Rust guarantees strict aliasing, such that the compiler can optimize more aggressively than ever possible in C.
    C is per definition also using strict aliasing, now many compilers took until C99 to actually implement it but it's there.

    Comment


    • Give some more time for the Rust shit show to really develop ...

      https://utcc.utoronto.ca/~cks/space/...ncompatibility

      Comment


      • Originally posted by F.Ultra View Post
        C is per definition also using strict aliasing, now many compilers took until C99 to actually implement it but it's there.
        Yeah, it's in the standard since C99, but who uses it? It's incredible insecure, because the programmer has to say: "I promise here is no pointer aliasing". How often do you see the restrict keyword in function parameters? I have never seen them in the wild. So in theory C has the feature, but almost no one uses it, because if the condition is violated, you have undefined behaviour.

        Comment


        • Originally posted by sdack View Post
          No. These are not analogies, but examples of simplicity.
          You realize that you're defying your own argument? You specifically said that:
          Originally posted by sdack View Post
          Fire, wheel, blade, hammer, ...

          Those are ancient and are still going strong.

          You better be ready to add C to this list.
          You brought up hammer not as an example of simplicity but as an example of an old tool that is still widely used. You pivoted to this simplicity thing only when your original argument failed because it was pointed out to you that even hammer has evolved from a rock on a stick to something more sophisticated.

          Originally posted by sdack View Post
          It is because of simplicity that C is still going strong and has outlived more complex languages. It is just more sad that you do not see this even when one compares C to a hammer.
          You're making stuff up. C simple - or perhaps "more primitive" fits better - design is not the reason why the language is still relevant today. If you check out StackOverflow language popularity surveys, you'll find Rust ranking very high on the charts of "Loved" and "Wanted" languages. C, on the other hand, is not doing so hot...

          https://insights.stackoverflow.com/s...age-love-dread
          https://insights.stackoverflow.com/s...nguages-wanted

          Comment


          • Originally posted by Raka555 View Post
            Give some more time for the Rust shit show to really develop ...
            Every language has had its teething problems. What your example shows, however, is that programmers will keep making mistakes no matter what tools you give them. Rust nor any other overbearing language will ever fix this. You might as well put a scorpion on your keyboard in hope that it makes you type more carefully and so turns you into a better programmer.

            Comment


            • Originally posted by MadCatX View Post
              You realize that you're defying your own argument? You specifically said that: ...
              I told you no and am still telling you no. When you cannot read what I write and do not want it explained nor have the intelligence to understand it on your own then I cannot help you. If you want to be stupid, be stupid.

              Comment


              • Originally posted by Steffo View Post
                How often do you see the restrict keyword in function parameters? I have never seen them in the wild. ...
                In case you want to see some do a fgrep restrict /usr/include/* It should show up as __restrict, but it is just a define and is needed to work with older compilers.

                Comment


                • Originally posted by sdack View Post
                  In case you want to see some do a fgrep restrict /usr/include/* It should show up as __restrict, but it is just a define and is needed to work with older compilers.
                  Yeah and it's not that much restrict I see...

                  Comment


                  • Originally posted by Volta View Post
                    Hopefully this mit licensed crap won't be picked by Linux distributions.
                    Linux sucks.

                    Comment


                    • Is there any info about binary size and memory consumption? Maybe rust coreutils can save some flash memory space or fit better into RAM of embedded devices.

                      Comment

                      Working...
                      X