3 ms·
WebKit and Mozilla simply refuse to implement many of the APIs because they cant' figure out how to prevent them from being abused. See e.g.https://webkit.org/
by dmitriid 6y ago
WebKit and Mozilla simply refuse to implement many of the APIs because they cant' figure out how to prevent them from being abused.
See e.g.https://webkit.org/tracking-prevention/#anti-fingerprinting https://webkit.org/tracking-prevention/#anti-fingerprinting (Mozilla's positions are more spread out over various issues, see e.g. https://webapicontroversy.com https://webapicontroversy.com )
- pjmlp 6y agoExcept Firefox is getting irrelevant, with Edge Chromium overtaking it, and Apple naturally would rather developers to use iOS APIs exactly for the same purpose, while collecting some revenue in Apple hardware for development purposes.
- dmitriid 6y ago> Except Firefox is getting irrelevant, with Edge Chromium overtaking it And this is a huge problem. > and Apple naturally would rather developers to use iOS APIs You're missing the point where Firefox agrees with Apple on these APIs. But sure. "Apple bad" and all that.
- deltron3030 6y agoFF should focus on a better UX. Try FF and Edge on Windows 10, Edge seems much snappier because it boosts the mouse scroll speed. A friend wanted to switch because of that, and increasing the overall mouse scroll speed on W10 did the trick for FF. It's little tricks like those that make non techy people switch.
- pjmlp 6y agoI don't agree with "Apple bad" at all, if you see my comments history. My point was that contrary to Mozilla, they do have an agenda regarding how much Web Safari should support on iOS.