2 ms·
They are now because they both use those APIs. You can read about the impact of this specific one here: https://mozillagfx.wordpress.com/2019/10/22/dramaticall
by st3fan 7y ago
They are now because they both use those APIs. You can read about the impact of this specific one here:
https://mozillagfx.wordpress.com/2019/10/22/dramatically-reduced-power-usage-in-firefox-70-on-macos-with-core-animation/ https://mozillagfx.wordpress.com/2019/10/22/dramatically-red...
Before using those private APIs, with no other options to reach the same performance as Safari, both Chrome and Firefox were in a completely different league.
- jolux 7y agoCALayer and IOSurface are not private...
- Null-Set 7y agoCALayerHost and CAContext were listed in the offending apis in this rejection of an electron app https://github.com/electron/electron/issues/20027 https://github.com/electron/electron/issues/20027
- jolux 7y agoAre those mentioned in the Mozilla post?
- kalleboo 7y agoFirefox does not use CALayerHost. It uses the public IOSurface and CALayer.contents APIs. https://mjtsai.com/blog/2019/11/04/electron-apps-rejected-from-the-mac-app-store/#comment-3103388 https://mjtsai.com/blog/2019/11/04/electron-apps-rejected-fr...
- threeseed 7y agoIt is ridiculous to say that Chrome/Firefox are only popular now because they use private APIs. Your own article says that Firefox only recently started using them.