1. 56
  1.  

  2. 6

    Awesome article. Very in-depth.

    1. 2

      I have an impression that when you run this ‘new fast engine in ******’ on older hardware, it will be the same sluggish program as it was before implementing new approach. It is just illusion created by faster and more efficient processors :)

      1. 4

        The ability to make proper use of those faster and more efficient processors is already quite the improvement none the less.

        1. 1

          Yes, it could be interesting to compare builds of firefox or chrome compiled by e.g. 10-years old and recent gcc or clang.

        2. 2

          Where’d you get that impression? My understanding is that it’s universally faster.

          1. 1

            My mother’s old two cores Athlon64 based computer gets updates regularly (it has ubuntu installed) - just 10 years old machine. She uses Firefox and I don’t feel that it has any improvement. I think that you may notice some speed up on recent hardware as new engine may be better optimized for new instructions or use more threads, which are not available on the older one.

            1. 1

              Your mother is using a nightly Firefox build? Quantum things are bound to land in stable in Firefox 57, which has a release date middle of November.

              1. 1

                Of course she is not using nightly builds. But as far as remember, Firefox is improving every stable release, so I assume that I (or my mother) should see these improvements on the old machine.

                1. 2

                  These improvements aren’t in stable yet, only in nightly, so if you’re not using nightly, then you’re not testing these improvements.

                  1. 2

                    That makes sense, thanks!