Over the years I've had my differences with the Chrome team in Waterloo that eventually made this possible; I argued that tools to make this sort of thing possible should have shipped years earlier. And I still think that.
-
Over the years I've had my differences with the Chrome team in Waterloo that eventually made this possible; I argued that tools to make this sort of thing possible should have shipped years earlier. And I still think that.
But that's not what's holding the web back; Cupertino is:
CSS property: animation-timeline: `scroll()` | Can I use... Support tables for HTML5, CSS3, etc
"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
(caniuse.com)
-
@bramus @owa Apple's starvation of the Safari/WebKit team hasn't just meant that important features like scroll-linked animations remain AWOL for many years, but that the show-stopping bugs make "available" features a perpetual mine field:
An Abridged History of Safari Showstoppers - Webventures
TL;DR: iOS Safari is more than an inconvenience for developers, it's the fundamental reason interoperability has been stymied in...
Webventures (webventures.rejh.nl)
This is a rolling catastrophe because of the #AppleBrowserBan
If FruitCo were *explicitly* trying to make the web irrelevant, what would it do differently? I struggle to come up with a better strategy.
-
@bramus @owa This forced monoculture of failure benefits only one party: Apple.
By requiring every developer to build native apps through a lack of features and reliability, the App Store maximizes rent extraction.
And by preventing real browser competition, Apple ensures that no competitor can ever displace Safari in practice. Turns out that's worth ~$20BN/yr:
-
@bramus @owa When I say that "platforms are competitions", this is what I mean.
Requiring that every web developer accommodate their failson engine, while returning a pittance to engine investment, is profit maximizing for Apple.
The bugs you're working around? The polyfill you're adding? They have only one beneficiary.
-
@bramus @owa It's easy to memory-hole, but Apple *really did* try to kill PWAs this year, and when it failed, they *really did* try to frame regulators for their dirty deeds:
Home Screen Advantage - Infrequently Noted
Cupertino's attempt to scuttle Progressive Web Apps under cover of chaos is exactly what it appears to be: a shocking attempt to keep the web from ever emerging as a true threat to the App Store and blame regulators for Apple's own malicious choices. By hook or by crook, Apple's going to maintain its home screen advantage.
Infrequently Noted (infrequently.org)
All of this is being done to protect rent extraction by app stores.
-
@slightlyoff @owa
Your posting about open independent web has devolved into non stop Apple bashing. I think it’s a bad look for a Microsoft browser engineer to constantly attack a single named competitor, but couch it in terms of defending “the open web”. -
-
@bramus @owa Yes, Google is doing nasty stuff to prevent the web from breaking out too (and it has the same "strategic inaction" flavour):
But the difference in the landscape is night-and-day. Apple's suppression of the web is singlehandedly preventing browsers and PWAs from providing an open, interoperable alternative to app stores. And that's intentional.
-
@slightlyoff @bramus @owa I can only speak to Chrome, but we're doing a lot of work to make PWAs better/encourage PWA use right now.
-
️