Safari is adopting an extensions API similar to Firefox’s WebExtensions

Re:Safari is adopting an extensions API similar to Firefox’s... by kgermino on Tuesday June 23, 2020 @01:39PM (#23617379)

Why is Firefox slower on a Mac? I know Safari is (supposedly) faster than a lot of the other options, but I haven’t seen anything about Apple slowing down other browsers on Macs[0].

[0] I know they force all browsers to use the same webkit engine as Safari on mobile devices, and used to limit competitors to an older slower version for “security reasons” but AFAIK they don’t slow down competitors on mobile anymore and never have on Macs

[ Parent | on HN ]

Re:Safari is adopting an extensions API similar to Firefox’s... by quantummkv on Tuesday June 23, 2020 @02:02PM (#23617734)

It's not Apple that slows down Firefox on Mac. It's just that Firefox cannot match the resources that apple and google throw around on their browsers. Firefox has to be economical on where their resources are directed towards. And understandingly Macos specific optimizations not the top priority.

[ Parent | on HN ]

Re:Safari is adopting an extensions API similar to Firefox’s... by MintelIE on Tuesday June 23, 2020 @06:45PM (#23621333)

They didn't have to rewrite everything in Rust thereby harming performance to a large degree.

[ Parent | on HN ]

Re:Safari is adopting an extensions API similar to Firefox’s... by saagarjha on Tuesday June 23, 2020 @09:19PM (#23622779)

That's not how Rust works.

[ Parent | on HN ]

Re:Safari is adopting an extensions API similar to Firefox’s... by MintelIE on Wednesday June 24, 2020 @08:50PM (#23635602)

>checks benchmarks And that's why I disagree. Also old-school Firefox and Seamonkey run great on my P3 450.

[ Parent | on HN ]

Re:Safari is adopting an extensions API similar to Firefox’s... by est31 on Tuesday June 23, 2020 @06:22PM (#23621111)

One component was Safari using unofficial APIs. But some of these unofficial APIs have since been used by both Chrome and Firefox as well.

[ Parent | on HN ]