Text only | Text with Images

ElkArte Community

General => Chit Chat => Topic started by: radu81 on January 04, 2018, 07:11:10 pm

Title: Firefox Quantum
Post by: radu81 on January 04, 2018, 07:11:10 pm
I used Firefox for years, between 2004 and 2010, then I switched to Chrome because it was much faster, especially with lots of opened tabs. When a major release of Firefox is released I test it on my PC for a few days and usually came back to Chrome.
Well, today I tested for a few hours the new version Firefox Quantum, and for now I am amazed with the performances. Who knows, probably this time I will return to FF. ;)

So what do you think about the new Firefox Quantum?
Title: Re: Firefox Quantum
Post by: ahrasis on January 04, 2018, 08:02:43 pm
I have both installed but mainly I am using chrome. The new FF is good but most of the extensions have become useless since its arrival.
Title: Re: Firefox Quantum
Post by: live627 on January 04, 2018, 08:48:38 pm
I don't get micro stutters when scrolling after the upgrade.
Title: Re: Firefox Quantum
Post by: Feline on January 04, 2018, 09:00:14 pm
The new FireFox is very bad .. many, many css fails and other.

But .. the Microsoft Edge is a good option side by side with Chrome ..
Also I tested the Edge on a Android Smartphone ... Not bad !

Fel
Title: Re: Firefox Quantum
Post by: ahrasis on January 04, 2018, 09:10:17 pm
Oo... I haven't had any issues with css though. And I seldom use Edge though I do think it's quite good too.
Title: Re: Firefox Quantum
Post by: live627 on January 04, 2018, 11:23:45 pm
at least it's not IE :P
Title: Re: Firefox Quantum
Post by: Frenzie on January 06, 2018, 10:35:38 am
I like Fx 57 better than I expected given that it breaks so much in the form of add-ons.

Quote from: Feline – The new FireFox is very bad .. many, many css fails and other.
Do you mean regressions or nothing specifically related to the "new" Fx 57 part of that? The previous time we almost discussed this (https://www.elkarte.net/community/index.php?topic=4585.msg33009#msg33009) no concrete examples were given.

Just to be argumentative, I'll say that the new Chrome is worse than ever, with heaps and tons more CSS and JS fails. :D I'll also give a concrete example:

https://bugs.chromium.org/p/chromium/issues/detail?id=571297 (back in 2015/2016, they broke visual viewports)
https://bugs.chromium.org/p/chromium/issues/detail?id=767388 (in 2017, they broke it yet again)

To be fair, Intel bothered to fix at least one of the various WebKit/Blink regressions I reported a few years ago before I gave up. Yes, Intel. Not Google, not Apple, not Opera. Intel. I had no idea they were even doing anything with browser engines. :)

Opera used to fix most bugs I reported pretty much in the next snapshot before they switched to Blink. That was nice. Oh well.

I could never even figure out how to report any bugs about IE. Nowadays there's a simple enough http://issues.microsoftedge.com and there's a "Send feedback" right there in the menu. They probably even listen. :P
Title: Re: Firefox Quantum
Post by: radu81 on January 06, 2018, 01:19:12 pm
after a couple of days I can say they surely improoved speed and memory usage. I have the bad attitude to open lots of tabs, with the older versions of FF I noticed a lot of RAM used and FF became slower. With the latest version I see they solved or partially solved this problem. If it's faster than Chrome I'd say probably no, but is much faster than the older versions. I didn't made any speed test, all based on my impressions.

On elkarte forums I didn't noticed anything wrong with FF until now. I noticed some websites are much slower to scroll up and down with FF rather than Chrome, and a couple of websites were displayed different in FF ...
Title: Re: Firefox Quantum
Post by: live627 on January 06, 2018, 07:10:38 pm
@Frenzie could these problems have stemmed from scheduled releases? (I don't know, that's why I ask)
Title: Re: Firefox Quantum
Post by: Frenzie on January 07, 2018, 06:25:18 am
@live627 The example I linked is a conscious and completely unnecessary decision to break compatibility. They even write proud blog posts about their BS like this: https://developers.google.com/web/updates/2017/09/visual-viewport-api

(Okay, actually that blog post is pretty neat. The problem is not the new API, but the associated breaking of the old one. But it's not an accident.)

And then in a year, someone will come by and say that Firefox' proper, unbroken implementation is a "JS fail"…
Text only | Text with Images