Announcement

Collapse
No announcement yet.

Firefox 68 Performance Is Looking Good With WebRender On Linux

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

  • #31
    Originally posted by Weasel View Post
    Yeah, but people who use Rust have differently-wired brain. Only such brain would use Rust. And they tend to write this kind of inefficient code. And well... forced bounds checking and fat pointers...
    Haha, our favorite C troll again. Who doesn't know what it's talking about.

    An advanced rust developer knows how to avoid safely avoid bound checks. And hey, bound checks are good, by the way. At least when doing safety critical stuff. Ada uses them as well, and that's what used to drive the space shuttle and other things which may not fail.

    And fat pointers? Nobody forces you to use Rc or Arc. Simply use references. Or plain C pointers, if you have to.

    But the fat pointers, like they are implemented in rust make more sense than their c++ counterparts. As the refcount is on the same cache line.

    Comment


    • #32
      Originally posted by oleid View Post
      Haha, our favorite C troll again. Who doesn't know what it's talking about.
      But facts are on my side bish. Firefox's C++ code is/was way worse than other browsers, precisely because they have rusted brains to even design Rust. They've always had it, but now they felt like making a language for their rusted brains...

      Originally posted by oleid View Post
      An advanced rust developer
      That's an oxymoron. Any advanced developer wouldn't use Rust after all.

      Comment


      • #33
        Originally posted by Weasel View Post
        But facts are on my side bish. Firefox's C++ code is/was way worse than other browsers, precisely because they have rusted brains to even design Rust. They've always had it, but now they felt like making a language for their rusted brains...

        That's an oxymoron. Any advanced developer wouldn't use Rust after all.
        You seem quite helpless.

        Comment


        • #34
          Chrome always had and still has the fastest and most responsive engine. AFAIK it it written in C/C++. So there is no excuse for Firefox being slow. A different programming language won't change the fact that they need to write better code.

          Comment


          • #35
            Originally posted by zoomblab View Post
            Chrome always had and still has the fastest and most responsive engine. AFAIK it it written in C/C++. So there is no excuse for Firefox being slow. A different programming language won't change the fact that they need to write better code.
            Chrome also has a few orders of magnitude more resources behind it (both, in terms of devs, and "monetary").

            Comment


            • #36
              I can't get MotionMark to work in Firefox on Linux. It always hangs at some point (the animation remains still, although the browser itself is responsive). This happens even with WebRender disabled. Anyone else got this too?

              Comment


              • #37
                An important note about MotionMark performance under Firefox: https://webcache.googleusercontent.c...&hl=en&ct=clnk

                Meta issue on Bugzilla about the same subject: https://bugzilla.mozilla.org/show_bug.cgi?id=1416082

                Comment

                Working...
                X