Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 39

Thread: Mozilla Firefox 22 Is Now Available

  1. #11
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    241

    Default

    Quote Originally Posted by schmidtbag View Post
    Yes and no. If a task is single threaded, multiple cores don't matter (I'm not sure if FF is). If you're using a CPU architecture with shorter pipelines than it's previous generation (such as Bulldozer), frequency is less important. If you aren't using all 4GB of RAM, then memory makes little impact - especially in a web browser, where you'll be spending more time waiting for the internet than you would for your memory to clean up.


    Either way, I'm getting the impression FF is now the new IE. MS seems to be paying a lot more attention to IE now that they realize everyone is blaming them for holding back the internet.
    Firefox uses currently 48 threads my system.

  2. #12
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,485

    Default

    Quote Originally Posted by grigi View Post
    No, I'd say Chrome is the new IE. it implements things differently than any other browser. There are now these sites that only work right in Chrome and nothing else.
    Well, unless proven otherwise, those sites aren't Chrome-exclusive due to Chrome being an under-developed piece of crap; in other words, it isn't suffering compatibility problems in the way that IE used to. Note that no browser is perfect and all of them have some advantage over the other, but Chrome is in pretty good shape.

    Firefox is definitely not holding anything back, it is still much more able than IE10, has better compatibility and usability than either Opera or Safari. True it isn't the speed king anymore, but I don't notice it getting slower at all either.
    True, FF isn't really holding back the internet and in some ways, defines what the internet becomes without actually being the industry standard. I would also agree that it's compatibility is better than Opera and Safari, though I personally like Opera much more. I haven't really used FF as a main browser since the version 3 days, so I can't really comment if it has improved in performance and memory usage.

  3. #13
    Join Date
    Oct 2009
    Posts
    2,145

    Default

    Quote Originally Posted by grigi View Post
    No, I'd say Chrome is the new IE. it implements things differently than any other browser. There are now these sites that only work right in Chrome and nothing else.
    That's an interesting, but flawed observation. Typically, those sites that only work in "chrome" are actually sites that only work in stoogfari. They also work in chrome because it uses the same crappy rendering engine (khtml, or whatever anyone else feels like calling it).

    Firefox is definitely not holding anything back, it is still much more able than IE10, has better compatibility and usability than either Opera or Safari. True it isn't the speed king anymore, but I don't notice it getting slower at all either.
    The "ie flaw" that was the cause of it holding back the internet was that it was limited to one flawed platform, and closed source.... pushed by a monopolistic bunch of dimwits, who FORTUNATELY, are well on their way in their move into irrelevance. No, Rome won't fall overnight, but fall it will, and on its way, it is.

    Firefox is the ONLY web browser that actually works well (performance) in Android. Compared to built-in/chrome, rendering performance is on a whole other plane of existence.

  4. #14

    Default

    Quote Originally Posted by bwat47 View Post
    I don't have any of these problems with firefox on a 2.5ghz dual core. In fact when it comes to smooth scrolling firefox is the best performing browser I've used (chrome's scrolling is atrocious even with the smooth scroll flag, and chrome's smooth scroll doesn't work at all with the middle click universal scroll, and also doesn't work on certain webpages, its pretty ridiculous for a browser in 2013 to have sich poor scrolling). This is the main reason I take firefox over chrome any day of the week. When it comes to stability, page rendering speed and such I barely notice any difference between firefox and chrome. Chrome's UI is slightly more responsive under load but thats about it. When it comes to memory usage I've found chrome to actually be significantly more memory hungry than firefox (although this doesn't really bother me either way, I have 8gb ram)
    Firefox can't even scroll for me, it's so choppy.

  5. #15
    Join Date
    Sep 2012
    Posts
    369

    Default

    Quote Originally Posted by droidhacker View Post
    ... compared to what?

    At least its not slow-like-chrome. That bitch is useless-slow.
    Both Firefox and Chrome work great on my dual core.

  6. #16
    Join Date
    Jan 2011
    Posts
    426

    Default

    Firefox (21) doesn’t crash often at all here, but it does crash on some game/physics JS engines demos.

    I have to agree that the most annoying “feature” of FF is its mono-threaded design causing an unresponsive UI during page loading.

  7. #17
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,939

    Default

    Firefox is working just fine here on an i5 Sandy Bridge, dualcore + HT, 4GB of RAM. No crashes, no hangs, no choppiness, nothing -- and thats with a lot of addons installed.

    Those of you having problems... bug in FOSS drivers (if youre using them)? Corrupted profile? Something else hogging CPU/GPU? Bad combination of addons?

  8. #18
    Join Date
    Mar 2011
    Location
    Canada
    Posts
    107

    Default

    Quote Originally Posted by stqn View Post
    Firefox (21) doesn’t crash often at all here, but it does crash on some game/physics JS engines demos.

    I have to agree that the most annoying “feature” of FF is its mono-threaded design causing an unresponsive UI during page loading.
    It's most definitely not "mono-threaded", take a look at all the threads it uses (tip: threads don't appear as processes).

  9. #19
    Join Date
    Aug 2011
    Location
    Hillsboro, Oregon
    Posts
    138

    Default

    Hooray! Firefox with proper Flexbox support...at long last :)

  10. #20
    Join Date
    May 2010
    Posts
    684

    Default

    Quote Originally Posted by strcat View Post
    It's most definitely not "mono-threaded", take a look at all the threads it uses (tip: threads don't appear as processes).
    The biggest problem afiak is that the chrome/compositing runs on the main thread. The firefox devs are working on off the main thread compositing though afiak which should help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •