News for hackers. Stuff that matters.
Re:Firefox 70 by freediver on Tuesday October 22, 2019 @12:07PM (#21325301)
I am not a Firefox user but know that matching Webkit performance on macOS is going to be very hard.

So just fired a test on my Macbook Air - Safari 13 vs Firefox 70.

Opened top 10 links from techmeme. Both windows in background.

Firefox 70: Energy use 30-200; CPU 20-25%; Threads 82

Safari 13: Energy use 0.1-5; CPU 2-5%; Threads 11

If this is to celebrate I can only imagine what the things looked like before this release. Save for Apple fiddling with the energy use numbers (VW style) this means that my battery is going to last 4-5x longer with Safari. Can anyone replicate this for the sake of argument?

Edit: uploaded screenshots https://imgur.com/a/4L64ShP

Re:Firefox 70 by jacurtis on Tuesday October 22, 2019 @12:13PM (#21325380)
> this means that my battery is going to last 4-5x longer with Safari

Well it might last 4-5x longer if you run safari in the background, since that is what you tested. But wouldn't the real test be running both browsers as the active window and comparing those results?

One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and windows to nearly zero. This is really good when running on battery because it is a shame to dedicate resources to things that aren't even visible on screen. But this could make the results far more dramatic through your test.

I would hypothesize that Safari still wins your performance test (if you were to re-test using them both as "active" windows), but probably not as dramatically as in the inactive window test.

Re:Firefox 70 by freediver on Tuesday October 22, 2019 @12:26PM (#21325544)
I used that use case because I usually have multiple windows with multiple tabs in the background.

I measured it with active windows now.

Screenshots:

- Both in background

- Safari Actie

- Firefox Active

https://imgur.com/a/4L64ShP

Conclusion: it gets even worse for Firefox.

Edit: At the time of test Safari had 7 more windows open with probably 70+ tabs from my previous session that I didn't close.

Re:Firefox 70 by devit on Wednesday October 23, 2019 @10:37AM (#21335038)
You are not running uBlock Origin, so ads might be taking up all the CPU cycles they can get their hands on.
Re:Firefox 70 by tomaskafka on Tuesday October 22, 2019 @01:52PM (#21326651)
> One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and windows to nearly zero.

I understand this is rare, but I just have a very very hard time understanding what is so hard about this.

Page not visible? Just stop it. Stop the layout engine, stop the javascript VM. If there was a transfer in progress, let it finish, a page might get the callback when it's active again ...

(I know there are some tricky cases, a lot of them, but there just isn't any reason why a browser with 30 tabs should be consuming over 1 % cpu...)

Re:Firefox 70 by freddie_mercury on Tuesday October 22, 2019 @10:54PM (#21330626)
Classic HackerNews "

This is so easy and I, a software developer with no actual experience in that area, know the obvious solution that eludes that hundreds of developers with actual experience in the area. Meanwhile, I take umbrage when my product manager tells me that implementing the next feature will be easy and I'm exaggerating how complicated it is."

Re:Firefox 70 by theonemind on Wednesday October 23, 2019 @12:22AM (#21331011)
Perhaps so. But,

if (not_visible) { suspend_wait_and_stop_consuming_resources }

I can imagine that it gets massively more complicated. However, as, say, an executive, this probably indicates that you can lean on your sw dev staff to approach the asymptotic ideal that looks so simple if you really care about the goal.

Re:Firefox 70 by icebraining on Wednesday October 23, 2019 @04:24AM (#21332442)
Of course, and all major browsers have background tab throttling features[1]. But there are multiple goals and limited dev time.

[1] E.g. Firefox added some in version 58: https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibi...

Re:Firefox 70 by paulintrognon on Wednesday October 23, 2019 @09:23AM (#21334341)
Reminds me an old boss I had who, when I reported a complicated problem, always came up with: "why don't you just write if (problem) { solution(); } ? Should'nt take long, should it?

Well, the difficult part is not writing an if statement...

Re:Firefox 70 by littlestymaar on Wednesday October 23, 2019 @03:22AM (#21332011)
> Page not visible? Just stop it. Stop the layout engine, stop the javascript VM. If there was a transfer in progress, let it finish, a page might get the callback when it's active again

Contrats, you just broke the web for anyone doing one of the following:

- listening to music in the browser.

- having a webRTC chat with someone while browsing.

- keep reading another tab while waiting for a page to load.

And I'm probably missing a dozen of other totally legit use-cases.

Re:Firefox 70 by squiggleblaz on Wednesday October 23, 2019 @08:28AM (#21333847)
"- keep reading another tab while waiting for a page to load."

Oh tell me about it. That's just about dead now. I mean, wasn't the point of multi tab browsing that I could do precisely that? Now I load Google Maps on my lethargic internet connection, go do something else for ten minutes, and come back and ... it starts loading when I open. This is on Firefox. Super sad.

Re:Firefox 70 by littlestymaar on Wednesday October 23, 2019 @11:24AM (#21335566)
Pretty surprising. I don't use Google maps though, but it works fine with all the websites I go daily.
Re:Firefox 70 by pmontra on Tuesday October 22, 2019 @02:11PM (#21326862)
YouTube music video running in another tab. Should it stop render the video and keep playing the audio? Maybe feasible but it should keep receiving both the video and audio data. Stop all of it? Not what I wish to happen.
Re:Firefox 70 by GrayShade on Tuesday October 22, 2019 @04:12PM (#21328064)
Firefox does stop rendering videos in background tabs (or used to, at least). You can see it take a couple of frames to restart.
Re:Firefox 70 by dwaite on Tuesday October 22, 2019 @03:00PM (#21327331)
The javascript engine and rendering engines are what are generally affected by being backgrounded. So yes, generally the media library will continue receiving the combined video/audio stream and not bother rendering the video frames
Re:Firefox 70 by roca on Tuesday October 22, 2019 @08:50PM (#21330012)
Youtube uses the Media Source Extensions API, which means that JS is responsible for fetching compressed video data and feeding it into the decoder, so it can implement adaptive streaming. Pause JS for more than a few seconds and the video will stop playing.
Re:Firefox 70 by dwaite on Wednesday October 23, 2019 @05:29AM (#21332826)
Yes, and this is likely why Youtube now periodically pauses in the background on current macOS/Safari.
Re:Firefox 70 by ripdog on Tuesday October 22, 2019 @11:45PM (#21330867)
My understanding is that most video websites like Youtube use Media Source Extensions, a standard which allows javascript to download and assemble video streams in non-standard ways. This work is done by page JS and passed to the browser to decode and render. AFAIK youtube uses this to implement DASH streaming.

Presumably there is no easy way to disable page JS but keep your youtube video downloading.

Re:Firefox 70 by tass on Tuesday October 22, 2019 @07:25PM (#21329506)
Does HTML video need to catch up based on the most recent keyframe?

If they don't render while backgrounded, how do they do that without being noticeable?

Re:Firefox 70 by vrodic on Tuesday October 22, 2019 @10:48PM (#21330596)
Chrome does this for a long time now and I don't consider it an issue. You see a frozen version of the last decoded keyframe until the next one is decoded. Elegant solution IMO.
Re:Firefox 70 by tass on Tuesday October 22, 2019 @11:24PM (#21330762)
That makes sense, it seems I haven’t looked closely enough to notice.

I couldn’t find info on how often a keyframe is expected from YouTube, but I’m recalling the bad old divx days where you sometimes had a frame per scene and skipping was very slow.

Re:Firefox 70 by baby on Tuesday October 22, 2019 @06:33PM (#21329132)
What about a timer running in a different tab?
Re:Firefox 70 by mrob on Tuesday October 22, 2019 @08:58PM (#21330048)
How can the browser distinguish between useful background Javascript (e.g. web based chat) and harmful background Javascript (e.g. advertising)?
Re:Firefox 70 by vrodic on Tuesday October 22, 2019 @10:46PM (#21330589)
It might not be perfect, but allowing only web workers (if you agree on getting push notifications from a page) might be the solution.
Re:Firefox 70 by ebg13 on Tuesday October 22, 2019 @12:32PM (#21325614)
> But wouldn't the real test be running both browsers as the active window and comparing those results?

No matter what you're doing, all but one of your tabs will be in the background at any given moment.

Re:Firefox 70 by jdironman on Tuesday October 22, 2019 @07:19PM (#21329460)
What about 4 windows, 2 for safari, 2 for FF in windowed mode? But I guess only window can be active at a time.
Re:Firefox 70 by HunOL on Wednesday October 23, 2019 @03:18AM (#21331987)
> One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and windows to nearly zero. This is really good when running on battery because it is a shame to dedicate resources to things that aren't even visible on screen. But this could make the results far more dramatic through your test.

Does it mean that page in background isn't updated in Safari?

Re:Firefox 70 by pfranz on Tuesday October 22, 2019 @01:15PM (#21326148)
I just can't imagine Firefox will ever be performant as Safari. One is written for a single platform developed at the same company that develops the hardware and OS (I'm not trying to belittle the Safari team--it's kind of amazing what they do). The other is developed separately, must equally support at least 2 other OSes and has an expectation for supporting older setups.

My problem is that Safari won't work for me as a daily driver so it's not an option. It seems too aggressive in memory management and in reloading.

So I'm very happy to see Firefox improve performance over Firefox-v1.

Re:Firefox 70 by saagarjha on Tuesday October 22, 2019 @06:22PM (#21329049)
WebKit also works on other platforms.
Re:Firefox 70 by deaddodo on Tuesday October 22, 2019 @07:03PM (#21329352)
You're thinking of Blink. WebKit is pretty exclusive to macOS and iOS these days.
Re:Firefox 70 by saagarjha on Tuesday October 22, 2019 @07:12PM (#21329414)
No, I'm not; I'm actually typing this from WebKit on Linux. I'd actually guess that WebKit runs on more platforms than Blink does…
Re:Firefox 70 by deaddodo on Wednesday October 23, 2019 @01:14AM (#21331298)
I didn't say it didn't run on other OSes. But the big ones are mostly iOS and it shows in the targeting of the development. Blink is what's on most (non-gecko/servo) browsers people use now (chrome, chromium, Opera, the new Edge browser, etc).

> I'd actually guess that WebKit runs on more platforms than Blink does…

I'd say they're probably at parity, if not a small edge given to Blink since an entire OS is built around it. Which would be the only exclusive case of the two I can think of.

I'm actually curious which WebKit browser you're using. GNOME Web?

Re:Firefox 70 by saagarjha on Wednesday October 23, 2019 @01:24AM (#21331352)
Yes, I was using GNOME Web.
Re:Firefox 70 by deaddodo on Wednesday October 23, 2019 @01:32AM (#21331387)
Interesting. You're one of the few people I know on Linux not using Chrome/Chromium or Firefox (or one of it's derivatives). And the others I know mostly use Konqueror.
Re:Firefox 70 by ekianjo on Tuesday October 22, 2019 @07:52PM (#21329692)
No, Webkit used to be a cross platform renderer which work started on Linux in the first place, so it is definitely not MacOS only.
Re:Firefox 70 by deaddodo on Wednesday October 23, 2019 @01:16AM (#21331316)
I never said it was Mac only. I said it's development now was mostly focused on iOS browsers. You can obviously use GNOME Web and the like, but most big browsers (especially cross-platform) that aren't Gecko-based are Blink-based (Chrome/Chromium, Opera, Edge beta)
Re:Firefox 70 by citilife on Tuesday October 22, 2019 @08:43PM (#21329961)
Even back in 2014, I was developing my own browser with webkit:

https://austingwalters.com/simple-web-browser-in-cpp-using-q...

Works on any OS I've tried.

Re:Firefox 70 by deaddodo on Wednesday October 23, 2019 @01:21AM (#21331343)
I never said it wasn't cross platform. I said it's development and use was pretty exclusive to iOS these days; outside of less common browsers like GNOME Web.
Re:Firefox 70 by Angeo34 on Tuesday October 22, 2019 @10:27PM (#21330492)
Webkit mother is literally KDE code.
Re:Firefox 70 by deaddodo on Wednesday October 23, 2019 @01:20AM (#21331337)
WebKit was based off KHTML. It hasn't been the same engine for 17 years (though they do occasionally share code) and never used the same jS VM.

Nice bit of obscure knowledge that adds nothing to the conversation. Unless your argument is that KHTML and WebKit are the equivalent to Blink because of a shared ancestry; in which case you're arguing something I never claimed.

Re:Firefox 70 by inferiorhuman on Tuesday October 22, 2019 @11:19PM (#21330736)
I just can't imagine Firefox will ever be performant as Safari.

Firefox has (for now at least) a huge leg up in terms of content blockers. IDK if that's enough to even out the energy consumption and performance, but it can't hurt.

Re:Firefox 70 by pfranz on Wednesday October 23, 2019 @04:31PM (#21338665)
I know Firefox is the one browser who isn't switching to the newer, more restrictive method of content blocking, but wasn't the (purported) motivation for Safari's change performance?

For my use, I keep many many tabs and windows open. Most of the efficiency gains I see are from handling that better. I don't use desktop Safari heavily. I tend to keep it as the thing I use when I suspect adblockers are messing up content (it's easier than disabling adblock). On my iPhone I do use an adblocker and haven't noticed problems. When I do browse the web without an adblocker I quickly recoil and think, "do people really live like this??"

Re:Firefox 70 by inferiorhuman on Wednesday October 23, 2019 @09:42PM (#21340887)
wasn't the (purported) motivation for Safari's change performance?

Maybe, but what kind of performance hit will letting all the ads and nonsense through be? I probably could aim to find a trusty ad blocker for Safari, keeping in mind that Apple has left the disingenuously named uBlock up in their extension store. Or I could just stick with uBlock Origin and a browser that works with it.

I've got ~2000 tabs open in Firefox right now and don't feel like performance or battery life is a problem. I use 1Blocker on iOS, but it's clunkier, less effective, and more expensive than uBlock Origin (and I still get tons of in-app ads). That's not something I'm in any hurry to bring over to the desktop.

Re:Firefox 70 by pfranz on Thursday October 24, 2019 @01:31AM (#21341902)
I can't speak to actual performance impact. I saw people flame Safari, then Chrome about the change. I was waiting to see how everything settled out for my own use case and switch browsers as needed.

> (and I still get tons of in-app ads)

I'm pretty sure that's expected. 1Blocker's FAQ says it won't work with most third party iOS apps like Chrome.

I'm sure usage varies and I'm glad Firefox works well for you. I have Firefox 70 hidden with about 7 windows and 40 tabs (total) and Activity Monitor points to it as the highest energy suck bouncing between 15-20 of whatever units this measures--in line with CPU usage. I only installed uBlock Origin last night for Firefox. I use it mostly for work stuff which generally doesn't have ads. Chrome, where I'm typing this is about 1/3 to 1/2 the usage (and it's not hidden).

I was hoping for more of an improvement from Firefox. Historically, using Chrome or Safari will get me literally hours longer between charging.

Re:Firefox 70 by willtim on Tuesday October 22, 2019 @12:53PM (#21325886)
IIRC Safari achieves this by suspending the processes in background tabs, which could be running inefficient JavaScript (polling for new ads etc). There's no cross-platform way to do this, but I think Mozilla absolutely need to try and find a way to address this. Web sites cannot be trusted to write efficient well-behaved JavaScript and so the burden of taming it falls upon the browser. There is probably some throttling going on, but clearly not enough. Running background JavaScript should be an opt-in permission, not the default.
Re:Firefox 70 by roca on Tuesday October 22, 2019 @08:56PM (#21330040)
Firefox can and does aggressively throttle JS in background tabs. However, it's not easy to do this in a way that doesn't break sites. Sometimes background tabs have JS doing actually useful work --- playing audio, running a simulation, receiving notifications, stuff like that.

I don't know what Safari is doing differently to Firefox, and no doubt Firefox can improve here, but when people say "it's easy, just completely stop running JS in background tabs" they have no idea what tradeoffs that entails. (Just as when people said "browsers should just refuse to autoplay videos" had no idea what they were talking about.)

Re:Firefox 70 by chii on Tuesday October 22, 2019 @09:58PM (#21330367)
When people comments "it'd easy to..." or "just so XYZ, it's simple", it means they haven't actually done the work before, and is just sprouting bs.
Re:Firefox 70 by mantap on Wednesday October 23, 2019 @10:03AM (#21334710)
The answer is simply that yes Safari breaks websites, but users are happy to make that tradeoff.

It's common knowledge among web developers that browsers aggressively throttle background tabs so anybody who is designing a website that depends on it is misguided.

I don't hear anybody complaining about Safari being too aggressive with background tabs, I do hear people complaining that Firefox uses too much battery. So I think Firefox should be more aggressive.

Re:Firefox 70 by roca on Thursday October 24, 2019 @06:11AM (#21343084)
A poll of your friends may not constitute adequate data for making such decisions. We know for sure that techie-people and friends-of-techie-people are qualitatively different to the mass market.

These tradeoffs may also be different for different browsers. E.g. if you're Apple, perhaps breaking Web sites isn't a big deal since on iOS Safari is entrenched by fiat, and if users switch from Web apps to native apps, so much the better for Apple. For Mozilla that calculation works out differently.

Generally speaking "site X breaks in Firefox, works in Chrome" is a good way for Mozilla to lose market share.

Re:Firefox 70 by plopz on Wednesday October 23, 2019 @01:11PM (#21336665)
Haven't people been complaining that youtube will randomly stop playing in the background on safari? I'm not so sure users are happy about that as you say.
Re:Firefox 70 by mantap on Wednesday October 23, 2019 @03:00PM (#21337708)
That sounds simple to fix by checking whether the tab is playing audio.
Re:Firefox 70 by Vinnl on Tuesday October 22, 2019 @01:47PM (#21326594)
There is an extension that does roughly this: https://addons.mozilla.org/en-US/firefox/addon/total-suspend...

(Not to say that it wouldn't be good if Firefox was better at it, but for those using Firefox, it might still be interesting until then.)

Re:Firefox 70 by mthoms on Tuesday October 22, 2019 @01:42PM (#21326534)
Firefox users should take a look at the "Auto Tab Discard"[0] extension. It offloads inactive tabs, saving CPU and RAM, (similar to how Safari works).

It doesn't work quite as transparently (or effectively) as Safari's equivalent functionality, but it does make a noticeable difference. It's worked very well for me.

[0] https://addons.mozilla.org/en-CA/firefox/addon/auto-tab-disc...

Re:Firefox 70 by BuckRogers on Tuesday October 22, 2019 @12:53PM (#21325888)
On Windows I've been testing the new MS Edge because I've noticed my laptop has significantly higher CPU usage running FF. The reduced battery life is one thing, a hot laptop is another. Currently the new Edge is not as well optimized as the original, but there's more to come on that front.

I've been using FF since it was in beta, never left but I'm starting to come around to the reality that native browsers are best optimized for the device. While there's no real native browser to leverage on desktop Linux, on macOS/Windows, native may be the best way to go for most people. This is how break down browsers to friends and family.

Google Chrome- optimized for Google's needs and profit margin.

Microsoft Edge- optimized for your device, if running Windows.

Apple Safari- optimized for your device, if running macOS.

Mozilla Firefox- optimized for the user. Certainly a noble goal, but I increasingly have a "mobile" goal and that trend isn't slowing for anyone.

Re:Firefox 70 by acqq on Tuesday October 22, 2019 @06:35PM (#21329151)
Yes, I also observe much more power drawn even on a single page (especially if it contains animations) opened in Firefox vs any other browser, and on Windows, IE is significantly less power hungry.

I've also checked this newest version, 70 on Windows and my measurement of the power use give practically identical results to the measurements I've done almost two years ago.

I see that the power drain comes from the browser's own code doing something unnecessary and as far as I see it doesn't even appear to platform dependent.

It's surely possible to optimize that and it's obviously not their priority.

Re:Firefox 70 by BuckRogers on Thursday October 24, 2019 @11:09AM (#21345410)
If you would share any of your findings, I'd be interested to see that.

From what I've read, Mozilla can't really optimize rendering to the level of Safari & Edge. I found this article[0] on WebRender to be very interesting on this front. The author noted-

"Note: Painting and compositing is where browser rendering engines are the most different from each other. Single-platform browsers (Edge and Safari) work a bit differently than multi-platform browsers (Firefox and Chrome) do."

I love Firefox quite a bit, every detail, the way it scrolls with smooth scrolling off, the dedicated search bar for switching DuckDuckGo bangs, the container support. The dedicated search bar is a huge one, I can't imagine why no one else at least offers that, as a feature it can't cause that much maintenance headache. I definitely love FF as much as anyone here but I'm not one who argues that Gecko is necessary for a standards-based web, I'm not convinced by the argument. Webkit can be forked again and it has a significant userbase to act as a counterweight to Blink. It's increasingly difficult at this point to convince myself that native browsers don't make the most sense.

[0]https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-f...

Re:Firefox 70 by acqq on Friday October 25, 2019 @04:31AM (#21352955)
My notebook happens to have a fan calibrated to turn on when the CPU gets "too hot" where the point is above of what is consumed by IE to show the pages with more videos, so I actually hear the power consumption of Firefox and I simply don't hear it for the same page when opened in IE.

So for me is simply: open some page, hear the fan for as long as the page remains open. Do the same with IE, silence.

BTW I otherwise haven't IE used for daily browsing, but I did a lot of tests with the same pages to see that it's not an accident and that IE does show the same content, but with less power used.

For somebody with a different computer: find any web page with more media playing on the page (you should see the videos playing or pictures "animating"), open the task manager (this is a Windows example) then switch to the graph view and compare the browsers while looking at the graph view. The task manager area "under the curve" reflects the power used -- the more CPU used for a given amount of time -- the more power used. In my observations the area drawn by Firefox is more that twice as big as the one by IE.

That's what drains the battery faster: taking more CPU to keep the "animations" on the page. Moreover Firefox has some consumption created by some of its background tasks even when the pages aren't animated, but the animations are really wasting a lot of power.

From my look at the behavior, having some experience in evaluating the performance of the software, and spending some time trying to figure out what's happening there, my impression is that the source of that power drain is in the Firefox code which is not platform specific which explains why they have problems on every platforms with that.

I've concluded they simply never actively tried to minimize overall CPU and GPU use (both will use more power unless somebody measures and tries to improve the code): even when they did move some pieces of processing to the GPU, their motivation was speeding up what's visible, actively minimizing the power used was simply not the part of their process.

You can also search their Bugzilla to see how they handle the problems with the CPU, GPU use and the power drain. This can be a part of the workflow, measuring that at least for every release and acting to fix the issues, but I just don't see that anywhere.

Re:Firefox 70 by BuckRogers on Sunday October 27, 2019 @02:21PM (#21371472)
That's essentially how I've been A:B testing as well. I was hoping you had some software that measured power draw and tracked it. Much like the Windows 10 power usage info. A laptop fan is a pretty good arbiter.

Agreed though, it's very noticeable and I never did feel it until I started using a laptop more than a desktop. I'm also finding bugs in the iOS version of Firefox which is probably going to be the last straw, not only does it freeze often, my bookmarks are no longer there and they were synced from my Firefox account. I'm likely to migrate to native browsers for whichever platform I'm on at that time. As you said in their own process they're focused on feature development but not efficiency. Overall, I'm losing faith that Mozilla has the resources to effectively manage all of this.

Re:Firefox 70 by BuckRogers on Thursday October 24, 2019 @04:31PM (#21348838)
I hate to followup with a 2nd response but I wanted to add, it really would be a poor priority anyway because they'll never be able to beat Apple or MS at optimizing a browser for their OS.

My advice to Mozilla would be to continue on the customizability and privacy route, and get Firefox on iOS in better shape. It's been freezing on me for as long as I can remember using it. Very buggy, and has played a significant role in losing some confidence in Mozilla.

This message and all of my messages in this thread posted from Microsoft Edge 78.0.276.20 (Official build) beta (64-bit).

Re:Firefox 70 by munmaek on Tuesday October 22, 2019 @12:23PM (#21325500)
Test: open 10 tabs of techmeme.com, on OSX Catalina (10.15 Beta), on a 2015 retina 13" macbook pro.

Firefox: Threads 71, %CPU 2.5. Energy: 0.4. Opening the tabs all at once took up ~68% CPU. Energy went up to 75.

Safari: threads: 8, %CPU: 0.7-2. When opening the tabs: %CPU: 28%. Energy usage: 2.4.

Firefox grew sluggish when opening that many tabs at once. Safari handled it like a champ.

Pretty bleak for firefox.

Re:Firefox 70 by billiam on Tuesday October 22, 2019 @01:41PM (#21326504)
Mozilla's priorities are (and have mostly always been) for FF on Windows. It's a gripe that me (and the great majority of FF devs who use Macs and Linux boxes) have been suffering under for years) that those OSs will just never be the highest priority--and the reasons why have much to do with Apple and their Apple-first mentality for their platform. It is only partly a joke that the last users of Firefox will be software developers and their grandmothers. But there are a lot more grannies than devs.
Re:Firefox 70 by daemin on Thursday October 24, 2019 @08:20AM (#21343871)
As other people have mentioned, Safari doesn't load/run tabs in the background. What happens when you switch to each of those tabs so you can use the site?
Re:Firefox 70 by paulcarroty on Tuesday October 22, 2019 @12:26PM (#21325551)
Something like this happens on my Linux laptop: Firefox eats battery 2-3 times faster than Chrome & cooler activity is much more higher.

Seems like Firefox cares only about Windows.

Re:Firefox 70 by pcwalton on Tuesday October 22, 2019 @12:53PM (#21325892)
> Seems like Firefox cares only about Windows.

…which is why all the work was done to support Core Animation on macOS?

Re:Firefox 70 by dwaite on Tuesday October 22, 2019 @03:05PM (#21327383)
To be fair, CoreAnimation was first released a year before FireFox 1.0.
Re:Firefox 70 by pcwalton on Tuesday October 22, 2019 @05:10PM (#21328535)
For many years CA wasn't hosted in the window server; it was rendered locally within the app via GL 1.x, which is worse than what Firefox was doing. And window server rendering didn't result in large energy consumption gains until Retina Displays came around.
Re:Firefox 70 by Khaine on Wednesday October 23, 2019 @07:08AM (#21333344)
Retina came about in 2012. That was 7 years ago!
Re:Firefox 70 by maximente on Tuesday October 22, 2019 @12:20PM (#21325469)
what would be interesting is running with state of the art ad blocking in safari (which IIRC they recently changed) and firefox with ublock origin on multiple domains so as to better approximate advertisement load across the web

i posit that ad blocking is actually a net resource saver, probably not at the level of using safari over firefox but certainly over unprotected firefox

(i am on gnu/linux or else i'd do this myself)

Re:Firefox 70 by Scarbutt on Tuesday October 22, 2019 @01:15PM (#21326155)
Safari is a high bar to reach but they are getting closer to Chrome.
Re:Firefox 70 by The_rationalist on Tuesday October 22, 2019 @12:50PM (#21325851)
Any number about chrome?