4 ms·

This is what happens when apple forces browsers to use Safari's rendering engine. Could it be better, sure. Use an OS that allows Firefox to use its own rende

This is what happens when apple forces browsers to use Safari's rendering engine. Could it be better, sure. Use an OS that allows Firefox to use its own renderer if it bugs you that much.

dbg31415 6y ago
So it's a Webkit issue? Honestly haven't got a clue what caused it. Just wish they'd fix it. Love all the privacy features of Firefox... but I have no inherent love for Gecko. Like that's all behind the scenes stuff. Does it matter, from a privacy perspective? Any insight into the aversion to using Webkit? Chrome uses Webkit on MacOS and Blink on Windows, yeah? Seems like the way to go. I want my Mac Hardware, it feels nice. I want to use Firefox, I trust it and I like that I can automatically clear cookies and history on close... The fact that Chrome pushes you to sign in is so fundamentally offensive to me. Just super-creepy. So I want Firefox on Mac, but I have no strong feelings towards Gecko one way or the other, if that's what's causing my computer to over heat... wish they'd just swap it out for Webkit.
- sjwright 6y ago
  Being Apple-built software, Safari/Webkit will always take advantage of all the hardware accelerated graphics capabilities and optimisations available in Mac laptops. Firefox/Gecko has an excellent rendering engine but Mozilla has often been late to the party with hardware acceleration on Mac. It's also worth noting that Safari doesn't necessarily support all the same video codecs as Firefox, so for example Zoom might be using hardware accelerated h264 in Safari whereas in Firefox might use a more advanced codec (e.g. VP9) for which your MacBook might have no hardware acceleration capability. If this is the case, Firefox ought to give users the option to disable support for these non-accelerated codecs when running on battery power.
- Lio 6y ago
  > So it's a Webkit issue? It's not a Webkit issue. The parent comment is confusing iOS with macOS and the rendering engine used by Firefox on macOS.
sjwright 6y ago
You're mixing up macOS and iOS. The user is referring to Firefox on a MacBook Pro where there are no restrictions on choice of rendering engine. You're also mixing up symptoms. If all browsers were forced to use the same rendering engine, you'd see little divergence of CPU/energy usage. The user is seeing a wild divergence—which is what you might expect when browsers are using different rendering engines. You're also mixing up talking points. People have accused Safari of being many things, but being profligate with CPU/energy usage is certainly not one of them.

This is what happens when apple forces browsers to use Safari's rendering engine. Could it be better, sure. Use an OS that allows Firefox to use its own renderer if it bugs you that much.

dbg31415 6y ago

So it's a Webkit issue? Honestly haven't got a clue what caused it. Just wish they'd fix it. Love all the privacy features of Firefox... but I have no inherent love for Gecko. Like that's all behind the scenes stuff. Does it matter, from a privacy perspective? Any insight into the aversion to using Webkit? Chrome uses Webkit on MacOS and Blink on Windows, yeah? Seems like the way to go. I want my Mac Hardware, it feels nice. I want to use Firefox, I trust it and I like that I can automatically clear cookies and history on close... The fact that Chrome pushes you to sign in is so fundamentally offensive to me. Just super-creepy. So I want Firefox on Mac, but I have no strong feelings towards Gecko one way or the other, if that's what's causing my computer to over heat... wish they'd just swap it out for Webkit.

sjwright 6y ago
Being Apple-built software, Safari/Webkit will always take advantage of all the hardware accelerated graphics capabilities and optimisations available in Mac laptops. Firefox/Gecko has an excellent rendering engine but Mozilla has often been late to the party with hardware acceleration on Mac. It's also worth noting that Safari doesn't necessarily support all the same video codecs as Firefox, so for example Zoom might be using hardware accelerated h264 in Safari whereas in Firefox might use a more advanced codec (e.g. VP9) for which your MacBook might have no hardware acceleration capability. If this is the case, Firefox ought to give users the option to disable support for these non-accelerated codecs when running on battery power.
Lio 6y ago
> So it's a Webkit issue? It's not a Webkit issue. The parent comment is confusing iOS with macOS and the rendering engine used by Firefox on macOS.

sjwright 6y ago

You're mixing up macOS and iOS. The user is referring to Firefox on a MacBook Pro where there are no restrictions on choice of rendering engine. You're also mixing up symptoms. If all browsers were forced to use the same rendering engine, you'd see little divergence of CPU/energy usage. The user is seeing a wild divergence—which is what you might expect when browsers are using different rendering engines. You're also mixing up talking points. People have accused Safari of being many things, but being profligate with CPU/energy usage is certainly not one of them.