new | show | ask | jobs Github

ezfe a day ago

iOS has many private APIs, this one is no different. The fact it's implemented in WebKit is a red herring.

▲

catsma21 a day ago | parent | next [-]

you failed to address the point of the comment you replied to.

▲

bigyabai a day ago | parent | prev [-]

So when Google creates self-serving APIs in a web browser engine, it's anti-consumer and is killing the free web.

But when Apple creates self-serving APIs in a web browser engine, it's just another private entitlement, a red herring and their right as the proprietor of Safari.

The lady doth protest too much, methinks.

▲

cosmic_cheese a day ago | parent [-]

The difference is that Google is by far in a much more dominant position and every dev who leverages Chrome-specific APIs further entrenches that dominance. In the browser space, Apple is the long-trailing runner-up and has far less impact.

It appears that this particular API is restricted to embedded webviews, too (doesn’t work in Safari), so it has no bearing on the open web, unlike APIs such as WebUSB in Chrome.

	▲	13 hours ago \| parent [-]
		[deleted]