macOS’s “Apps Using Significant Energy” list does a good job of listing Apple’s browser competitors but a poor job of listing the background process constantly spinning at 100% CPU.
-
-
Right, that explains the /effect/ (and how Apple’s own tools let you measure it), but there’s no magic or privilege going on. Rather, Apple has made different engineering priorities than Mozilla.
-
Safari uses certain system libraries (or kernel features, or something, I'm not exactly sure what) and the power consumption of those libraries don't get counted towards Safari's power consumption. Firefox and Chrome don't do that. That's the unfair part.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.